3 ms·
What's the alternative? Certainly multi platform native only makes sense at a certain scale. Your question might be too light on details to provide much advice
by goosejuice 2y ago
What's the alternative? Certainly multi platform native only makes sense at a certain scale.
Your question might be too light on details to provide much advice.
- knallfrosch 2y agoReleases should be automated anyway. Once you set up the necessary pipelines, there is not that much work involved. I think our only pain point (team of ~7 devs) is keeping a Macbook around for iPad builds and debugging. But I guess you will need Macbook to debug any Safari issues too.
- goosejuice 2y agoAre you referring to builds of a PWA wrapper shipped to the App store? If you don't mind sharing, how did your approval process go? Any hangups?
- knallfrosch 2y agoSorry for the confusion. We ship minimal Electron (Windows) / Cordova (iOS) wrappers to interface with our website. They're a pain to set up but don't require all that much code themselves. This allows us to publish to the respective stores. Would be hard to convince non-technical users to click "Install as PWA" because noone knows what that is.
- goosejuice 2y agoGood to hear. I've read a few companies who really struggled getting approved with this method. https://developer.apple.com/app-store/review/guidelines/#minimum-functionality https://developer.apple.com/app-store/review/guidelines/#min...
- carlosjobim 2y agoIf it's about making money or making a living, your best alternative is probably to make an app exclusively for the platform where most of your profitable customers are. You can expand to other platforms later if you get the scale.
- goosejuice 2y agoIn my experience that's always been the web, which is why PWA is so attractive. Especially now that Android allows you to basically publish your PWAs to the Play store.