docs: add FAQ about mobile apps #12761
Conversation
|
| @@ -102,6 +102,14 @@ If you need hash-based routing on the client side, check out [svelte-spa-router] | |||
|
|
|||
| You can see a [community-maintained list of routers on sveltesociety.dev](https://sveltesociety.dev/packages?category=routers). | |||
|
|
|||
| ## How do I write my mobile app? | |||
|
|
|||
| The [most popular solution](https://bitrise.io/blog/post/the-state-of-mobile-app-development-in-2022) for building mobile apps is to use the Android and iOS SDKs directly, which makes building a mobile app completely independent of which JavaScript framework you use. Similarly, the cross-platform Flutter library, which uses the Dart programming language, is very popular as well and [often preferred to other solutions](https://survey.stackoverflow.co/2024/technology/#2-other-frameworks-and-libraries). | |||
There was a problem hiding this comment.
this seems like a very weird paragraph to include in the Svelte docs. Surely in the context of this FAQ, 'How do I write my mobile app?' means 'How do I write my mobile app with Svelte?'
There was a problem hiding this comment.
yeah, I can see that. I was trying to address folks that would point at React Native by noting that usually you're not using JS to write a mobile app anyway. And while I'd like to highlight that solutions exist in Svelte, I honestly can't say I'd recommend them at this point
Maybe there's a better way to word it?
There was a problem hiding this comment.
Do we still want this PR? If there's nothing we want to recommend then maybe we don't need to say anything. If we do want this FAQ answered then the answer should probably mention Tauri
There was a problem hiding this comment.
I still think this is helpful. It's a complex ecosystem of different solutions and it helps people to provide some pointers and things to consider. Though the Svelte Native part might need to be updated
I looked at Tauri when writing this and it was completely impossible to write a mobile app in it. Even today I can't find any docs on how to actually do that. They even seem to acknowledge some of the short-comings here: https://v2.tauri.app/blog/tauri-2-0-0-release-candidate/#the-road-to-stable-and-beyond
There was a problem hiding this comment.
I mean, the RC blog post you linked to says this
we want to make clear that you can develop production ready mobile applications with Tauri NOW
and https://v2.tauri.app/start/ says this
Tauri is a framework for building tiny, fast binaries for all major desktop and mobile platforms.
so while I haven't personally done so it definitely seems like you should be able to (and Thilo Maier and Daniel Mader gave a talk on combining Tauri and SvelteKit at the last Svelte Summit, though they found some drawbacks).
Anyway, if you're still keen to get this in then let's ditch the first and last paragraphs, and point it at main
There was a problem hiding this comment.
Unless I missed them, there are literally zero docs for tauri mobile. Do we really want to tell people about something with no docs? Or can you find the docs?
There was a problem hiding this comment.
There was a problem hiding this comment.
I mean there are no mobile docs. That page doesn't mention anything about mobile. I guess I could mention something at the end about Tauri, but I'll caveat it quite heavily that it's in development, there are no docs, and you need to find your own way
There was a problem hiding this comment.
dev: https://v2.tauri.app/develop/#developing-your-mobile-application
distribute:
android: https://v2.tauri.app/distribute/google-play/
ios: https://v2.tauri.app/distribute/app-store/
i havn't tried it and the docs menu is a bit confusing to me but as far as i understand tauri v2 does support mobile apps and there are docs for it.
There was a problem hiding this comment.
Ah, cool. This is way better than what they had when I originally authored the PR and those pages were essentially TODOs. Their site search is really terrible. If you type "mobile" it doesn't come up. I'll file an issue to see if they can make it a bit easier to find
|
closing in favor of a PR against |
Sending this PR to the v4 branch
ref #9294
I think this could probably close that issue though understand some users are asking for more