Forem: Bayajit Islam

Learning Backend with Node.js: Running My First Server

Bayajit Islam — Mon, 10 Nov 2025 13:12:02 +0000

3 State Management Mistakes I Wish I Knew Earlier — By Bayajit Islam

Bayajit Islam — Tue, 04 Nov 2025 06:18:40 +0000

When I first started building Flutter apps, state management felt overwhelming.

I made some mistakes that cost me hours — here are the top 3 I wish I knew earlier 👇

1️⃣ Using `setState` Everywhere

At first, I used setState() for almost everything.

✅ Mistake: It caused unnecessary rebuilds and made debugging harder.

💡 Tip: Use ValueNotifier, Provider, or Riverpod for parts of the UI that don’t need a full rebuild.

2️⃣ Overcomplicating with Heavy Packages

I tried every package I found online — Bloc, MobX, Redux — even for tiny apps.

✅ Mistake: Overkill = slower dev + more boilerplate.

💡 Tip: Start simple: Provider or Riverpod is enough for most small to medium apps.

3️⃣ Not Planning App Architecture Early

I jumped straight into coding without thinking about how data flows.

✅ Mistake: Hard-to-maintain code, messy state, and bugs everywhere.

💡 Tip: Spend time planning state hierarchy: which widgets own the state, which widgets just listen.

📌 Key Takeaway

State management isn’t just about code — it’s about structure and efficiency.

Pick the right approach for your app size, and think about data flow early.

I’m Bayajit Islam, a Flutter frontend developer who loves building clean, maintainable apps.

Small mistakes early can save you huge headaches later 🚀

How I Optimized My Flutter App’s Performance by 40% — By Bayajit Islam

Bayajit Islam — Wed, 08 Oct 2025 03:40:57 +0000

When my Flutter app started lagging, I decided to fix it — not just patch it.

Here’s how I improved the performance by around 40% 👇

🧠 1. Found Rebuild Issues in DevTools

Using Flutter DevTools, I noticed some widgets rebuilding too often.

✅ Fixed it by adding const keywords and breaking large UIs into smaller stateless widgets.

⚡ 2. Switched to `ListView.builder`

Static Column → ListView.builder() = smoother scrolling.

Even for small lists, .builder() matters.

💾 3. Cached Images

Replaced Image.network() with CachedNetworkImage.

Instant load when navigating between screens!

🧩 4. Used `ValueNotifier` Instead of `setState`

For small UI updates, ValueNotifier + ValueListenableBuilder keeps rebuilds minimal and performance high.

🔄 5. Fewer Animations, More Speed

Cut unnecessary animations and used Lottie only where it added value.

Less GPU load = smoother UX.

📊 Result

Rebuilds ↓ 40%
Memory ↓ 30%
Smoother frame rendering ✨

Performance isn’t just about numbers — it’s about how the app feels.

Little tweaks make a big difference.

I’m Bayajit Islam, a Flutter frontend developer focused on fast, clean, and modern UI.

Let’s connect on LinkedIn, GitHub, Facebook, or Instagram.`

Hey Dev Community — I’m a Flutter Frontend Developer

Bayajit Islam — Tue, 07 Oct 2025 04:05:26 +0000

Hey everyone! I’m Bayajit Islam, a Flutter frontend developer who enjoys building smooth, responsive, and user-friendly mobile apps.

I spend most of my time working with Flutter and Dart, focusing on clean architecture, beautiful UI, and great performance. For state management, I usually go with GetX or BLoC, depending on what fits best.

Lately, I’ve been learning a bit of Django to understand how Flutter connects with backends — it’s been fun exploring the full picture of app development.

I joined dev.to to share what I learn, write about Flutter best practices, and connect with developers who love crafting great apps as much as I do.

If you’re into Flutter, architecture, or just learning new things — say hi in the comments!