There's a lot to consider before committing to a framework to build a native app. If you choose to build in native, ask yourself whether you're prepared to handle the downsides that come with it.  

To start, you're limited to one framework and writing in one programming language. If you're not familiar with the syntax, that could pose a major learning curve. With native apps, it's tempting to have a separate app for every device that a user might run your app on, but on the operations front, that's a slippery slope with high overhead costs. If you're on a tight budget or working on small teams like Chuck and Robbie, the cost of paying developers to maintain a bunch of apps isn't appealing. There's no shame in knowing your resource limitations and taking the easy route. 

In this episode, Chuck and Robbie talk about the trade-off between building native apps in Swift, Objective-C, React Native, and other web technologies, why they enjoy progressive web apps, and Disney's monopoly in media. 

Key Takeaways

Quotes

[03:16] - "It's crazy how no one has money because of the recession, and yet everything that you could possibly buy is super expensive and sold out all the time. It doesn't make sense." ~ Robbie Wagner [https://twitter.com/rwwagner90]

[23:04] - "You feel like businesses don't feel like they have a presence unless they're in the App Store." ~ Chuck Carpenter [https://twitter.com/CharlesWthe3rd]

[25:05] - "The one thing that has been that I've used as a progressive web app that's worked well is Google Photos." ~ Robbie Wagner [https://twitter.com/rwwagner90]

Links

See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.