BUILDING SERVER-DRIVEN MOBILE APPS FOR WEB3 WORLD
The world of web3 is a rollercoaster of innovation, pushing boundaries and evolving at breakneck speed. At OKTO, we’re building a bridge between this dynamic web3 terrain and the established web2 landscape. But bridging these worlds means mobile app development needs to shift gears – away from slow, siloed processes and towards the lightning-fast iteration of web3. This blog dives into how we built a server-driven UI framework capable of keeping pace with the web3 whirlwind.
WHY YOUR NEXT APP SHOULD BE IN FLUTTER
Mobile development has changed a lot in the last few years. In the past, if you wanted to build a fast, smooth app, you had to build native apps for both iOS and Android. Cross-platform apps were mostly web-based, slow, and unpolished. But now, things are different. Cross-platform solutions like Flutter can meet the needs of most products. In fact, it’s often better to start with Flutter and only move to native development if your product demands it.
THE RIGHT ABSTRACTION
It’s a very popular saying — abstract it out if you are duplicating it a third time. But when you make duplication the primary trigger for abstraction, it could lead to some problems. You should abstract something only if you have found the right way to abstract it. Recently, I came across some poor abstractions and decided to investigate their causes. Most of the time, poor abstractions often result from a hasty attempt to eliminate duplication.