3 ms·
On iOS there isn't always a choice to not build something native. For example, I can't install Navidrome as a PWA because Apple doesn't properly support audio p
by cdrnsf 8mo ago
On iOS there isn't always a choice to not build something native. For example, I can't install Navidrome as a PWA because Apple doesn't properly support audio playback for PWAs. I ended up writing a client that suited my listening habits.
To read ePubs, however, I was able to write a PWA leveraging epub.js because no native APIs were required.
- AnonHP 8mo ago> On iOS there isn't always a choice to not build something native. Tangentially, even native can be badly designed and developed, performance wise. Even Apple hasn’t been able to do a good job with the Reminders app (one of the several apps ported to Mac with the same level of negligence that Electron brings in). I use a lot of Reminders and lists in Reminders. It’s janky and poorly coded.
- cdrnsf 8mo agoOh absolutely. I hadn’t touched native development in perhaps a decade (and that was Xamarin before Microsoft acquired them). My initial iterations were rough, but I’m happy with where the app is. Choosing an audio app to try native again likely wasn’t the best choice on my part either.