3 ms·
How can you realistically avoid this for certain products though? For mobile for example, you've got the iOS and Android store policies to go through, the iOS a
by seanwilson 6y ago
How can you realistically avoid this for certain products though? For mobile for example, you've got the iOS and Android store policies to go through, the iOS and Android SDKs, and whatever restrictions Safari (e.g. no proper PWAs) and Chrome have.
Not everything can be a website that just needs basic browser capabilities.
- tonyztan 6y agoAt least Android allows sideloading without using the Play Store. Chrome used to allow this, and I believe they've made it much more difficult.
- deleted 6y ago[deleted]
- thejynxed 6y agoI believe you can only do it on the dev channel now and it still makes a fuss.
- viraptor 6y ago> How can you realistically avoid this for certain products though? You can't. It seems like if you're in business of mobile/web-apps which are not large enough to have paid, direct contacts with your relevant platforms, you should have more than one business. I'm not saying it's a reasonable expectation or a good thing. But if you can pull off either 2 ok apps, or 1 main app and some set of simple things, it may be preferable to one perfect product from the business continuity perspective.