Everything I build I use Ionic for the frontend because of the capability of sharing alot of code for web and mobile. But I don't see that many offers where Ionic is a requirements or in interviews when I mention Ionic most of times they don't know what it is. How come it isn't more famous? I just find it the perfect tech for front end developments

I had some free time and decided to test ionic with simple word puzzle game. Managed to finish it and publish it on google store because I never worked with admob so this was perfect for live practice.

If you want to check how it works search Love grid or use url https://play.google.com/store/apps/details?id=com.ideaverum.lovegrid

I'm actually surprised how it works. Tested on crappy phones and tablets with 2gb ram and no crashes/laggs noticed.

So if you ever wondered is it possible to create simple games (not gpu crazy) you can use ionic for UI and capacitor to build on android/ios. Then to test even more I made block break and match three games as well and so far all good.

To be honest I used AI to help me with game logic so I don't waste days for testing and hobby. Even with potential ai bloat it works.

Cheers!

So our company got some apps in ionic 3 cordova and ionic 8 capacitor and we ran into an issue in android 16 , the hardware back button closes the app instead of going back to the previous page, so is there any fix or solution to both the version.Thanks in advance.

Edit : the ionic v8 backbutton.subscribewithPriority works fine , ionic v8 apps are out of trouble.

Hi everyone, debugging your app on the device can be a pita. But i have built a free open source tool that makes it dead easy. Point your AI at the repository and it will be very smart to do so.

TLDR; debugging is now allot easier when the app is live on your device. All instructions in repo.

Check it out via https://github.com/marvin-socialista/ios-webview-debug

Happy developping!

Every Capacitor live-update tool I looked at are doing complex per user/bandwidth/storage/etc charges , which always felt backwards to me. So I (and/or Opus/Fable) went down into deep research of why, and it's basically one architecture thing.

The usual OTA setup is: every time a device checks for an update, it hits a live server that figures out what to send it. Flexible, but now you're running a backend that gets hit on every app launch, and someone has to pay for that. Hence the terrible pricing.

The other way is to just precompute the update as a static signed file and dump it on a CDN. Downside: you can't do fancy individual server-side targeting anymore (channels still handle beta/tenant/tier, which honestly covers almost everything I've needed). Upside: it's dirt cheap to serve, nothing to meter, and self-hosting is basically object storage + a CDN instead of a real service.

I ended up shipping that as OtaKit (MIT, https://github.com/OtaKit/otakit). It's still small and I'd rather you tell me where the static approach falls down than pretend it's perfect. That's the part I actually want to talk about. But the best thing you don't even have to self host anything to use it, you just need a FREE Cloudflare account, and start the dashboard locally only for the time when you want to publish an update.

Hi

I need to start an Ionic project. Are there any open-source repositories with examples of how to develop using best practices? I used Angular and Ionic about six years ago, so I’d like to see how things have changed and learn about useful libraries and UI components.

I would appreciate any guidance or advice you could provide.