Our Android App is Frozen in Carbonite
Our Android App is Frozen in Carbonite
After seven years of trying, we need to change course on our adventure in the Android galaxy.
The new requirements make sense only if there's the possibility to contact human support. Google unfortunately is run by bots
Surely at this point you'd make your own Google Drive and sync your notes to there? Clearly relying on a third party API isn't working for them financially so stop doing it. Some S3 storage and a backend isn't that difficult and could be run for pennies.
I'm not sure from this blog post why they can't do that?
Cuz they're shit programmers who can't think out of the box...who the fuck would use google drive in the first place?!???
It's asinine.
That's the first time I have seen "s3" and "pennies" in the same sentence. ;) Is it really true? I keep hearing about "excessive egress costs", doesn't that apply here?
I don't understand why there aren't more progressive web apps to combat this. Maybe the google drive integration would still be a problem, but you can avoid app store shenanigans by deploying directly to your users.
I've been working on Duet, an open source Getting Things Done task app. It's mainly developed as a PWA, with a working Android client.
I primarily only intented to distribute it as a PWA, but there are way too many problems with this approach:
- Since it's offline first, I had to find a suitable database that can be used locally. Browser level Implementation ended up being based on IndexedDB, and all was swell on Android, but it was dog shit slow on iOS because of a long standing bug in Safari that Apple has never fixed since iOS13
- PWAs work great on Android - but only when accessed and "Installed" via Chrome - Firefox support is nil (for any platform TBH), and other Chromium browsers don't have the same featureset for PWAs that Chrome does. Like for example, WebAPKs, which add a ton of niceties like launcher shortcuts, or "open in app" when browsing a supported link in Chrome. WebAPK has been claimed by Google to be released "shortly" since 2022, but so far, only Samsung's browser support a similar feature set, and I don't think they're using the same WebAPK standard that Google uses on Chrome
- Local notifications - there were proposals for support for this, but all of them fell through, and since Duet is offline first, I'd need to run a separate API server to facilitate push notifications (and also make it insanely difficult if someone wants to selfhost their own instance of Duet)
- PWAs suffer from limited resources on Android - initial versions of Duet wasn't actually offline first, and communicated with a self-hostable API server, and the app itself was written in Vue. The scrolling and UI animations were extremely janky when Vue was managing deep reactivity for a bunch of things. In fact, if you run the PWA version of Voyager for Lemmy, you'll notice the same thing. This isn't there on iOS, and moving the PWA into an WKWebView or WebView instantly makes it more responsive without any changes in code at all.
- File access - PWAs can't access the local filesystem. This is probably for the better, but I seem to recall there's a standard for it being discussed.
PWAs work well for any sort of situation where you have online experiences like shopping or the like - Walmart's Flipkart have a really good PWA built in React Native for Web and is often showcased as the best example of React Native and React Native Web by the RN team
The moment you want to make a slightly more complex app like a productivity app or similar, you'll find it very hard to work with a PWA and would want a native counterpart.
Not to mention that any sort of filesystem access pretty much requires you to have a hybrid app - either through React Native, or Expo, or Capacitor.
Maybe Firefox dropping pwa support is a factor there?
You're limited on UX when it comes to PWAs. For tools where this matters a lot, PWAs are a non-starter.