Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Sign in
Join
4
Likes
5
Comments
How to choose a platform for your mobile app
by
Adriaan Mulder
https://medium.com/input-logic/how-to-choose-a-platform-for-your-mobile-app-733ee49fda6c
I love writing PWAs. I do not agree with "limited offline capabilities". I have made a music player that plays youtube videos offline, that is, blobs of media content. The issues with PWA in that regard are that you need a knowledgeable user who doesn't go and wipe their offline storage willy nilly, because that would be dumb. Another issue there is the platform differences between e.g. iOS and android as they behave differently and that puts limitations on what it should be use it for. Many app-like features have issues, e.g. I experimented with location API a while back and sure it works, but on iOS you are going to have to explicitly enable it from settings and average user will not jump through those hoops. iOS also doesn't prompt to install while Android does. On desktops there is a little (+) icon, so it's there but somewhat muted. However, for any type of "simple" implementation this is my #1 goto.
Native apps is my second goto, but takes longer to build. I would not touch RN with a stick, which is funny because I write all PWAs in react. RN is something else though. Honestly I thought this article would have 4 platforms being: native, RN, flutter and xamarin.
I see people post this type of articles on reddit quite often. I would recommend this general advice: choose a platform from the ones you know because you want to be aware of the limitations before you decide, and make a sound decision of what will work best. If you do not know any then default to native.
Thanks for the feedback! I also love PWAs and it's my preference for personal projects. I'd avoid native at all costs and try the wrapped PWA approach for any native SDK requirements or just to get it in the app store. I don't have any experience with Apple's approval process on these wrapped apps though.
Good to hear you had success with offline storage, something I haven't spent much time with.
Apple will not let you pass wrapped, my cofounder is iOS dev. Their process is super strict about this.
I understand avoiding native because it duplicates effort. It works for us because we split the load equally with one dev doing android and one doing iOS. It makes upgrading easier down the road.
Anyway, thanks for sharing this article.
Don't forget about Xamarin, Flutter, Ionic, Cordova!
This was written by a co-worker. I think it could be valuable to anyone about to venture into building a mobile app.