I'm thinking about the mobile app in terms of how already. But it's definitely on the roadmap.
ArkHost
Electron came first and has a massive ecosystem. Most apps were built before Tauri was mature enough. Switching frameworks is expensive, so existing apps stay on Electron. New projects are increasingly picking Tauri though.
Tauri is an alternative to Electron. Both are frameworks for building desktop apps with web technologies, but Electron bundles a full Chromium browser (which is why Electron apps use so much RAM). Tauri uses your OS's native webview instead, much smaller, much lighter. Both are open source. The difference is resource usage.
Obsidian's default editor is barebones, you need plugins to get a usable experience. HelixNotes gives you rich editing out of the box: formatting toolbar, slash commands, source mode toggle. No setup. It's also not Electron. Rust + Tauri 2.0 & Svelte fraction of the RAM, launches instantly. Same philosophy though: local .md files, no cloud, no lock-in. If Obsidian works for you, no reason to switch.
Mac Cmd shortcuts fixed in v1.1.0, just shipped. Thanks for reporting it.
Thanks for all the feedback everyone. Just shipped v1.1.0 based on what was reported here today:
- Obsidian wiki link import fix
- macOS Cmd key shortcuts (was showing Ctrl)
- Frontmatter no longer modified on notes you don't edit
- KaTeX math support
- Daily Notes
- Tag management (single + batch)
- View mode toggle + focus mode improvements
- Source mode search
- Notebook delete confirmation
- Collapsible sidebar tags
Not like Typora, no. HelixNotes has a WYSIWYG editor and a source mode toggle, two separate views. Not inline markdown rendering.
You have both - the WYSIWYG editor and a way to switch to the Markdown editor.
AI is optional, disabled by default, and doesn't even show in the UI unless you enable it. The app works fully offline with zero AI involvement.
Not at this moment. Which local model would you like to see as an additional option?
Great! Thanks for the feedback.
All 3 enhancements noted. Will be implemented in next release.