iOS support: constraints and proposed path
Supporting iOS for mdnx is primarily a distribution and licensing challenge rather than a purely technical one. Apple’s App Store terms impose restrictions that conflict with the freedoms required by GPL/AGPL software, which is why GPL-licensed apps have historically faced compatibility and enforcement issues on the App Store.
In addition, iOS distribution differs significantly from desktop platforms. Large-scale consumer distribution outside the App Store is generally not available, with sideloading options limited to specific regulatory environments (such as EU-only alternative marketplaces under the Digital Markets Act) or enterprise-managed deployments.
Because of these constraints, embedding the full AGPL mdnx engine directly inside a native iOS App Store binary may not be a viable path. Instead, the current working approach is to support iOS via a Progressive Web App (PWA) running the mdnx engine compiled to WebAssembly. Modern iOS browsers support WebAssembly execution, making it possible to run the real engine locally while avoiding App Store licensing conflicts.
The expected initial mobile experience will therefore focus on the workflows that matter most on the go: capture, reading, search, and lightweight edits, while the full desktop application remains the primary environment for heavy editing and knowledge management. If demand is strong, a thin App Store companion client may later be explored to add native integrations (for example share-sheet capture or notifications), while preserving the open local-first architecture.
Any iOS app is almost certainly going to be a paid app to cover the costs of providing apps for the app store.
To make the license for any iOS app FOSS but compatible with the app store it would likely be MIT licensed.
If iOS support is important to you, please 👍 react to this issue so we can gauge interest and prioritize work accordingly.
iOS support: constraints and proposed path
Supporting iOS for mdnx is primarily a distribution and licensing challenge rather than a purely technical one. Apple’s App Store terms impose restrictions that conflict with the freedoms required by GPL/AGPL software, which is why GPL-licensed apps have historically faced compatibility and enforcement issues on the App Store.
https://www.fsf.org/blogs/licensing/more-about-the-app-store-gpl-enforcement
https://www.gnu.org/licenses/gpl-faq.html#AppStoreCompatibility
In addition, iOS distribution differs significantly from desktop platforms. Large-scale consumer distribution outside the App Store is generally not available, with sideloading options limited to specific regulatory environments (such as EU-only alternative marketplaces under the Digital Markets Act) or enterprise-managed deployments.
https://support.apple.com/en-us/117767
https://developer.apple.com/app-store/review/guidelines/
https://digital-markets-act.ec.europa.eu/
Because of these constraints, embedding the full AGPL mdnx engine directly inside a native iOS App Store binary may not be a viable path. Instead, the current working approach is to support iOS via a Progressive Web App (PWA) running the mdnx engine compiled to WebAssembly. Modern iOS browsers support WebAssembly execution, making it possible to run the real engine locally while avoiding App Store licensing conflicts.
https://webkit.org/blog/5852/introducing-webassembly/
https://webkit.org/
The expected initial mobile experience will therefore focus on the workflows that matter most on the go: capture, reading, search, and lightweight edits, while the full desktop application remains the primary environment for heavy editing and knowledge management. If demand is strong, a thin App Store companion client may later be explored to add native integrations (for example share-sheet capture or notifications), while preserving the open local-first architecture.
Any iOS app is almost certainly going to be a paid app to cover the costs of providing apps for the app store.
To make the license for any iOS app FOSS but compatible with the app store it would likely be MIT licensed.
If iOS support is important to you, please 👍 react to this issue so we can gauge interest and prioritize work accordingly.