Why We Don't Build Native Apps.
Why I Chose PWAs Years Ago—And Why You Should Consider Them Too"I have chosen Progressive Web Apps a while ago, several years ago actually, and I’m extremely happy to have chosen this. And I want to explain to you why."The Problem: Small Teams, Big ChallengesA few years ago, I faced a tough decision—how to build the best possible user experience for my product while keeping development efficient. Like most small companies, we had limited resources; budget, time, and engineering capacity were constraints we couldn’t ignore. And yet, users expected seamless, high-quality experiences across devices.Maintaining separate web, iOS, and Android applications wasn’t an option. It was clear that splitting focus would slow us down, increase costs, and create an inconsistent experience for users. But what was the alternative?The Turning Point: Why PWAs Made Sense"Having a native app and a web experience or even multiple native experiences is not efficient at all, and it is not great for the user experience."That’s when I realized that Progressive Web Apps (PWAs) offered a way forward. With a single codebase, we could provide a consistent experience across devices, reducing development and maintenance efforts.It wasn’t just about the technical aspects but also about aligning product and tech strategies. We needed a solution that made sense from a business and user perspective.The PWA Edge: What It OffersPWAs are not just about offline capabilities—although that’s a bonus. They offer everything we expect from modern applications:* Cross-platform compatibility; No separate development for iOS, Android, and web.* Instant updates; No App Store delays.* Better performance; Compared to hybrid frameworks like Flutter and React Native, the web is lightweight and fast.* Lower costs; One team, one codebase, less complexity.This was a game-changer for small teams. Instead of spending time maintaining multiple versions of the same app, we could focus on building the best possible user experience faster.The Alternative: Do Native Frameworks Solve This?"When you take into consideration what modern native frameworks can do, like Flutter or React Native, and then compare that to web technologies, you’ll see that most applications small teams build are better suited for the web."I understand the argument for native apps. Flutter, React Native, and other frameworks promise a “write once, run anywhere” experience. However, they still have compromises. Flutter’s web performance is lacking, and React Native requires bridging for native functionality. Both also demand extra layers of complexity compared to a well-built web app.Do I need a highly specialized native feature? Solutions like Capacitor bridge the gap. But for 95% of use cases, PWAs did everything I needed—and more.The Outcome: A Simpler, More Scalable ApproachWe shipped faster. We iterated quicker. And we kept our team focused. The best teams are small, efficient, and aligned. Having one codebase, one product, one experience keeps everything streamlined. It’s not about being dogmatic; it’s about choosing the best tool for the job.PWAs have matured. Even Apple, once reluctant, has finally acknowledged them. If you’re starting a new project, ask yourself: Do you need a native app, or is a PWA the better choice?Key Takeaways* PWAs reduce complexity; One codebase means fewer resources spent on maintaining multiple platforms.* Better for small teams; Focus on product quality, not platform-specific bugs and fixes.* Instant updates & control; No App Store approvals, just ship whenever you need.* Bridges exist for native needs; Capacitor and other tools can fill in gaps where necessary.* Future-proofing: Web technologies will be here in 20 years, but the same can’t be said for every framework.What’s Your Experience?Have you built a PWA before? Do you still maintain separate web and native apps? Or do you believe native apps are worth the trade-offs?Let’s talk in the comments.First Session: Monday, 17 March 202517:00 CET | 11:00 AM EST | 08:00 AM PSTEvery Monday at the same timeTopics for This Session:🍪 What is the right team size?Why bigger isn’t always better and how to structure teams effectively.🍪 How I align teamsCutting through resistance, enabling autonomy, and ensuring real collaboration.Each session will feel like a real mentoring call, not a lecture. I’ll share my approach and insights, but most importantly—I’ll take questions directly from attendees and focus on the real challenges you’re facing. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit blog.snackablecto.coach/subscribe
México