svelte-capacitor VS vite-aliases

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

@components, @store, and @utils: If you have ever taken a look at sveltekit they have these nify aliases throughout their code so you don't have to write '../../../components' or what have you. Now you can just do '@components/file' and Vite will readily load them from the components folder, this makes it easy to create changes as you don't need to change the file location on every move or copy. Please check out the Vite Aliases package for more questions.