- Web (IE, Safari, Firefox, Chrome, and older versions of those browsers)
- Web responsive (When you access it from small screens or access the web from your phone's browser)
- Android (old devices to recent ones)
- iOS (old devices to recent ones)
- And, eventually, get to a desktop app, ideally on windows, mac and linux.
Say you're the tech lead and you need to make a decision about the stack to support all these platforms, and you're a team of 2-3 devs, yourself included. What stack do you pick?Even Instagram didn’t even have an Android app until they were acquired, and then it still took them another couple of years to support web. Their focus was their success.
An Instagram launching today would see much greater pressure to be on Android sooner rather than later.
Personally, I find it amazing to have one engineer builds a feature end-to-end from the server to the web/mobile devices by using the same language and re-using 90% of the code across all the clients.
Perhaps windows is better? What about linux? :p But I see why people are disliking the native ui situation on desktop.
But I would want my media player, or chat application, or something that's meant to be a media-based experience to be well presented.