I'm building MarkdownVault, a native iOS app that saves web pages as encrypted Markdown on-device — no cloud sync, no tracking.
We're entering a TestFlight beta with ~20 testers and I need help validating five core paths before App Store submission.
Who I'm looking for
| Profile | You might be… |
|---|---|
| A — iOS dev | Swift/SwiftUI developer who reads technical docs daily |
| B — PKM user | Obsidian/Logseq user who wants offline web clipping |
| C — Content curator | Blogger/newsletter author working in Markdown |
Time commitment
~30 minutes. Five test paths: vault setup, URL conversion, offline mode, bounded crawl, export.
Opt in
Fill the short form (no Apple ID yet — TestFlight invites come after build is ready):
https://qveys.github.io/webpage-to-markdown/beta/
Out of scope (not bugs)
iCloud sync, multi-vault, Safari Share Extension, monetization, Android.
Tech stack (for devs)
Swift 6 · SwiftUI · iOS 18 · local encryption · URLSession + HTML parsing
Thanks for helping shape a privacy-first reading/conversion tool 🙏
Top comments (0)