3 ms·
That does involve writing two apps instead of one if you want to support ios and android though. Plus, some PWAs are really good. I much prefer facebooks mobile
by nicoburns 8y ago
That does involve writing two apps instead of one if you want to support ios and android though. Plus, some PWAs are really good. I much prefer facebooks mobile website to their app...
- briandear 8y agoSo write two apps. Android and iOS are different, have different capabilities and a market size that justifies the effort — assuming your app is worth a damn in the first place. This lowest common denominator development trend is obnoxious. Basically, it “socializes” the experience so that every device is treated equally despite devices having different strengths and weaknesses. We are trying to make devices conform to the app rather than the app conform to the strengths of the device.
- nicoburns 8y agoThere's a trade off here, right? Between focussing on these platform specific UX details, and actually implementing more functionality jn the app. Also: modern smartphones are very similar to each other. Sure there are differences, but for the most part they are minor.
- coldtea 8y ago>That does involve writing two apps instead of one if you want to support ios and android though. As a user, it's enough for me that you support one platform, the one I use, as best as possible.
- nicoburns 8y agoWell, it's not enough if the company decides to support the one that you don't use! Also, many apps that provide access to a service don't make commercial sense unless they are accessible from both platforms.