Kumar Harsh

indie apps & devrel

[Kumar Harsh @heykumarh]

If you're buying for where your support operation is today, a closed platform is fine. If you're buying for 18 months from now, audit the API surface before you sign.

Full breakdown of what to test before you commit: https://t.co/DiRTqILjdH

[Kumar Harsh @heykumarh]

Most teams pick knowledge base software by checking the editor, the widget, and how fast they can publish. That works at 50 employees. It breaks down once support and product start getting tangled together.

[Kumar Harsh @heykumarh]

The problem: most teams don't realize they've made an architectural choice until reversing it is too costly.

[Kumar Harsh @heykumarh]

Here's a full implementation guide, including how to wire this into a production CI/CD pipeline: https://t.co/ihh0Kmz2V7

[Kumar Harsh @heykumarh]

Since long, I've seen Flutter teams get stuck waiting 24-48 hours for App Store review every time a critical bug ships to production. React Native sidesteps this by swapping a JavaScript bundle at runtime. RN has long had this edge over Flutter

[Kumar Harsh @heykumarh]

Real world results:
- A payment flow crash gets fixed and deployed in minutes, not days
- Users get the patch silently on next app launch
- You skip the App Store queue entirely for code-level changes

[Kumar Harsh @heykumarh]

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👇 https://t.co/Jk0w9xwK1Q

[Kumar Harsh @heykumarh]

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. 🧵

[Kumar Harsh @heykumarh]

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

[Kumar Harsh @heykumarh]

If you're setting up a new Flutter environment, or auditing an existing one, this guide might save you some debugging time:
https://t.co/TgNNBHgHJz

[Kumar Harsh @heykumarh]

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.

[Kumar Harsh @heykumarh]

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.