Start in the browser before installing
The web editor is the quickest way to decide whether VeloWrite fits your writing style. Paste Markdown, switch between Write, Split, and Preview, then download a Markdown or HTML copy without creating an account.
This browser-first path is useful on a shared or locked-down Mac because it avoids installation friction. Once a draft becomes something you want to keep editing, the desktop app is the better place for local files and offline work.
A quick Mac test note
# Mac Writing Check
## What I want to verify
- The editor opens quickly
- Split preview keeps up while I scroll
- Code blocks and tables stay readable
- Export gives me a clean file
## Next step
If this draft matters, move it to the desktop app and save it as a local `.md` file.Use a short document first, then test a longer file with headings, tables, and code.
Understand the current DMG status
The Apple Silicon DMG is published only after a successful GitHub Actions build and after the release asset exists. The download page should not show a placeholder asset that users cannot actually install.
The current macOS preview is unsigned and not notarized. Gatekeeper may require an explicit open action during early testing. That is a release-trust limitation, not a Markdown editing limitation.
Use desktop when the Markdown file matters
The desktop app handles native open and save, recent files, offline work, and local history snapshots. Those features matter more on real documents than on quick browser drafts.
A good Mac Markdown workflow should make the file path clear, keep the source text portable, and avoid hiding your notes inside an account-only database. VeloWrite keeps that local-first direction visible in the current preview.
Local-first file habit
# Project Notes
## Local file
Save this document as `project-notes.md` inside a folder that is backed up by your normal system.
## Recovery habit
Before major edits, save once so the previous version becomes available in local history.This does not replace your backup system. It makes everyday editing less fragile.
What Mac testers should check first
Start with the practical path: open a Markdown file, edit a paragraph, save it, reopen it from Recent, export HTML, export PDF, and verify local history after a second save.
Test a longer reading session too. Switch the reading palette and preview font in Settings, then use Preview mode on a longer document. A Markdown editor needs to stay comfortable after five minutes, beyond the first screenshot.
Version visibility matters on desktop
A desktop preview should tell users what version they are running and whether a newer release exists. VeloWrite shows the installed version in About, and the download page lists the latest public installer version with its release date.
Automatic update installation will require a signed update channel before it becomes a fully trusted stable workflow. Until then, the safer preview path is visible update detection plus a clear link back to the official download page.
Preview limits to keep in mind
Treat the current DMG as an early preview. Back up important Markdown files, expect extra Gatekeeper friction, and report any file handling, export, or layout issue through the feedback form.
The priority is to make the free preview dependable for reading, editing, export, and recovery before paid Pro workflows become the main focus.