capacitor VS svelte-query

It should also be mentioned that the official VSCode Ionic Plugin is also capable of migrating your existing application. Capacitor v6 now also supports bun as a package manager.

> PWA optionally bundled with some native components for filing the gaps, as in Tauri.

Isn't that essentially Capacitor?

https://capacitorjs.com

Have you experienced slow scrolling issues?

https://github.com/ionic-team/capacitor/issues/4187

Project: Build This Webpage (just this one page, make sure it is responsive (useful on all screen sizes)) => https://capacitorjs.com/

Capacitor

For the longest time, building desktop apps was a daunting task to web developers. That is, until technologies like Electron made creating these apps more approachable to a wider audience. Today, we’ve got a wide array of native applications built with solutions like Electron, Tauri, Capacitor, and many more. While these are great solutions, sometimes configuration can be tricky and the applications we create can become somewhat bloated in terms of memory usage.

The traditional alternative to Electon on mobile platforms is Capacitor (which uses the system webview):

https://capacitorjs.com/

(fka Apache Cordova, fka PhoneGap)

Ionic Framework UI Components are used to build a website and then a mobile application is built using Ionic Capacitor. Ionic UI components are not required but are used for UX. The vue js code presented here will work fine in a separate application.

Welcome to Part Two of this four-part series on building a mobile game using open source technologies. We'll be using Phaser, along with Ionic, Capacitor, and Vue.

Nice I was waiting for this! I'm using the old implementation: https://sveltequery.vercel.app/

I'm aware there's another Svelte Query here but it seems like it is not maintained and will be incorporated into Tanstack Query.

Until then I use Svelte Query

I like React Query so I would be excited to use this however it doesn't seem ready for Svelte given the docs "Coming Soon" and Svelte Query being relatively unmaintained.

Svelte Query :)

Or just use svelte-query and toss that observable junk to the side.

Exactly. That's the big thing I want to work on next. Not sure whether to use Svelte Query or manually cache the data. In an ideal scenario all the API calls are cached because if two users hit the site at the same time, for instance, there's no need to request the same data twice. This is getting to the edge of my skillset but psyched to try to learn this part.

That's it. Nothing highly sophisticated. It is mostly the tech I enjoy and I think is valuable in the future. There are also other libraries I really enjoy, like XState and React Query (there is also Svelte Query). Just to mention a few.

Caching: svelte-query, sswr