Kumar Harsh

setState isn’t wrong. It just doesn’t scale. If your Flutter app is growing, you need structure before things get harder. Full guide on how to use BLoC with @shorebirddev below👇 dev.to/kumarharsh/the…

BLoC fixes this by separating concerns: events (intent), states (UI snapshot), and a BLoC layer that handles logic and emits state changes via streams. The UI stops guessing and simply reacts to the state. That predictability is why teams like Nubank and BMW use it in production

In Flutter, setState works fine for small apps. Once you add shared sessions, real-time sockets, or concurrent API calls, it starts to break down fast. 🧵

If you're setting up a new Flutter environment, or auditing an existing one, this guide might save you some debugging time: dev.to/kumarharsh/flu…

The guide also shows how to integrate @shorebirddev for over-the-air updates from day one. Many teams try to add OTA updates only after a production bug appears. But by then, it's too stressful. It's much easier to include it as part of the initial setup.

Most Flutter environments fail in the same three places. • Broken PATH variables • Missing Android SDK command-line tools • CocoaPods failures on Apple Silicon None of these problems is complicated, but they tend to appear when the initial setup skips a few steps.

I break down the technical architecture, security implications, and 5-year TCO analysis. This isn’t Hello World benchmarks. It’s what matters when you’re making infrastructure decisions that will stick around for a decade: dev.to/kumarharsh/rea…

Meanwhile, Flutter closed its deployment gap with @shorebirddev . The framework that already had better rendering consistency and supply chain security now has production-ready OTA updates without forcing you into managed build services.

The Microsoft App Center shutdown last March forced me to rethink the entire mobile framework landscape. When Microsoft killed CodePush, React Native teams lost their deployment infrastructure overnight. Most migrated to Expo EAS, which works but introduces vendor lock-in.

I compared the technical architectures, rendering pipelines, and OTA update mechanisms (with @shorebirddev ) to help you make an informed choice: dev.to/kumarharsh/flu…

The real decision now: Flutter gives you 20% lower maintenance costs and pixel-perfect consistency. React Native gives you access to a JavaScript talent pool that's 20x larger.

React Native's New Architecture achieves 92-99% latency reduction in native module calls through JSI. Flutter's Impeller eliminated shader compilation jank entirely. The performance gap that defined the Flutter vs React Native debate has largely disappeared in 2026.

Read the full tutorial on: dev.to/kumarharsh/flu…

This guide covers: - Installing @shorebirddev CLI - Creating your first OTA-enabled Flutter app - Understanding Flutter's widget tree and state management - Shipping releases and pushing live updates From zero to deployed in 30 minutes.

Waiting days for app store approval to push a critical bug fix is painful. So, I wrote a tutorial showing how to build Flutter apps with over-the-air code push built in from the start, using @shorebirddev !

If you’re evaluating mobile frameworks or just want a clearer mental model, this might help: dev.to/kumarharsh/wha…

I wrote a complete introduction that walks through how Flutter actually works. Rendering model, SDK layers, trade-offs, and where tools like @shorebirddev fit if you care about updating apps after launch.

I spent a long time watching teams build the same mobile app twice. Once in Swift for iOS, once in Kotlin for Android. Same features, same bugs, fixed in two places. It always felt inefficient, but it was treated as normal. 🧵