Mustafa Naser

Founder | iOS & Flutter Lead | Building the Agentic Future 🦂 | Synthesis over Information | Utilities Ai to keep up with Ai

[Mustafa Naser @sof9816]

@REMIX_KSA And then get a ban

[Mustafa Naser @sof9816]

@GlobeEyeNews Bro had to triple down on not joining

[Mustafa Naser @sof9816]

7/ The real metric isn't "lines of code."

It's "time to understand the codebase when you come back in 6 months."

Verbose but explicit beats clever but implicit every single time.

[Mustafa Naser @sof9816]

🧵 Your app works fine with 100 users.

But at 10,000 users, it crashes randomly. Memory leaks. ANRs. OOM kills.

Here's how to architect for scale from day one: ↓

[Mustafa Naser @sof9816]

6/ GetX is fast to write. GetX is also fast to create unmaintainable messes.

The "magic" that makes it convenient also makes it impossible to debug.

I've spent 40 hours debugging GetX issues that would have been obvious in Bloc.

[Mustafa Naser @sof9816]

4/ Bloc/Cubit is verbose. Bloc/Cubit is boilerplate-heavy.

But Bloc/Cubit SAVES your ass when the app grows.

The explicit state transitions make debugging 10x easier. The separation of concerns means you can refactor without fear.

[Mustafa Naser @sof9816]

3/ Provider was the gold standard. Now it's a footgun.

Why? Because it doesn't enforce architecture.

Your junior dev can (and will) put business logic in the UI layer. And you won't catch it until production.

[Mustafa Naser @sof9816]

2/ setState() is not your enemy—but it's not your friend either.

For simple counters? Perfect.

For a banking app with 47 screens and real-time sync? You're building a house of cards.

[Mustafa Naser @sof9816]

Scale breaks everything. Plan for it.

Follow @gt for mobile architecture insights 👇

[Mustafa Naser @sof9816]

7/ Test on garbage devices.

If it runs smooth on a 3-year-old budget Android, it'll fly on new iPhones.

Performance test on the worst hardware you support.

[Mustafa Naser @sof9816]

6/ The best optimization is not doing the work.

Pagination > Infinite scroll
Lazy loading > Eager loading
Local cache > Network request

Speed is a feature. Architect for it.

[Mustafa Naser @sof9816]

5/ Logging is debugging at scale.

Every crash should tell you:
• User ID
• Device info
• Network state
• Last 10 actions

Without context, crash reports are useless.

[Mustafa Naser @sof9816]

4/ State synchronization across devices is HARD.

Don't roll your own.

Use:
• Firebase (fastest to implement)
• Supabase (open source alternative)
• Realm (offline-first)

Building sync yourself is a 6-month project. Minimum.

[Mustafa Naser @sof9816]

3/ API polling is a scalability trap.

Instead of polling every 5 seconds:
• Use WebSockets for real-time
• Use push notifications for updates
• Cache aggressively with TTL

Your battery life (and server costs) will thank you.

[Mustafa Naser @sof9816]

2/ Images will kill your app.

That 4K image from the API? Resize it BEFORE displaying.

Use cached_network_image in Flutter.
Use downsampling in native.

Never load full-res images into memory. Ever.

[Mustafa Naser @sof9816]

1/ Memory is your enemy. Treat every object like it's a potential leak.

In Flutter: Use weak references for callbacks
In iOS: Use [weak self] in EVERY closure
In Android: Always nullify listeners in onDestroy

Paranoid memory management is good engineering.

[Mustafa Naser @sof9816]

10/ Your state management choice will outlive your features.

Choose wisely.

Follow for more architecture insights. What state management are you using? 🚀 👇

[Mustafa Naser @sof9816]

🧵 "Should I learn SwiftUI or stick with UIKit?"

I've shipped 8 apps to the App Store. Here's the honest answer nobody wants to give you: ↓

[Mustafa Naser @sof9816]

10/ Your state management choice will outlive your features.

Choose wisely. Choose for the team you'll have in 2 years, not the convenience you want today.

Follow for more architecture insights. What state management are you using? 🚀 👇