svelte-capacitor VS Svelte

Thanks for the suggestion! From the comments so far a Vite + Svelte SPA does seem like the way to go. Whilst I hadn't seen the repo you shared yet, but I was looking at this one: https://github.com/drannex42/svelte-capacitor. Would be keen to hear your thoughts on if one is better than the other.

I agree on going the PWA way (except for iOS quite easy, and iOS is doable), other than that there's still hybrid approaches. I stumbled upon this repo some time ago, maybe that's something to start with (using Capacitor, there's also NeutralinoJS, Tauri, and others)

I am planning on making a Svelte + Routify + Vite Mobile & Web App. And when choosing from options for mobile dev, I concluded from Reddit threads previous to this one, that Capacitor might be the best choice vs it's sole contender, the unmantained Svelte Native. I was btw planning on using [this template](https://github.com/drannex42/svelte-capacitor/tree/master/src) for that.

I develop a realrovely popular open source Svelte[1] related template (w/ live reload!) to develop cross platform apps.

Capacitor really is a beauty to work with. While I disagree on some design decisions (putting build platforms at the root of the directory for one) the overall ecosystem is quite healthy and strong, and while backwards compat with Cordova is hit or miss, its quite good for an old school tool thats a decade old.

[1]. https://github.com/drannex42/svelte-capacitor

Pretty much a combination of svelte-ionic-app and svelte-capacitor but without the extra code related to the examples in svelte-ionic-app

You can check it out here. I am always open to questions and PR's!

I built a fairly popular template for this: https://github.com/drannex42/svelte-capacitor

the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:

Svelte

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.