Day 51 #100DaysOfCode #React I made a grocery bud app that works like a Todo list. You can add, delete, and mark items as completed. The app saves your list in the web browser, so even if you close and reopen it, your items will still be there, where you left them. A thread 🧵

Today was one of those coding days… everything broke just as I was about to finish. 😭 Fix one error → 3 more appear. Rename a variable → IDE throws 9 red lines. Every dev knows this struggle. 💻 #100DaysOfCode #Flutter

5️⃣ I over-designed and under-tested I spent time making UI look “pretty” without testing interactions or edge cases. What I learned: Good UI is not just beautiful, it is: • Clear • Consistent • Accessible • Predictable • Fast • Simple to navigate

4️⃣ I didn’t separate UI from logic I wrote everything in one file: State + widgets + layout + business logic It was a complete mess. What I learned: Create reusable widgets and separate logic into: • Providers • Controllers • Services • State classes

3️⃣ I ignored responsive design My UI looked perfect on my phone… but terrible on larger screens. What I learned: • Use MediaQuery • Use LayoutBuilder • Use Flexible & Expanded Think in terms of ratios, not fixed pixel values Good UI adapts not breaks.

2️⃣ I didn’t understand constraints I wondered why my widgets overflowed, clipped, or refused to take full width. What I learned: Flutter UI follows a simple rule: Parents give constraints. Children choose size. Parents position children.

Use widgets for their specific job: • Padding for spacing • SizedBox for fixed size • DecoratedBox for decoration • Container only when combining multiple properties Messy UI + unnecessary rebuilds.

1️⃣ I used Container for everything If I wanted space → Container. If I wanted color → Container. If I wanted padding → Container. The result? What I learned:

Flutter gives you full control of the interface… but if you don’t understand the fundamentals, your UI will look confusing, inconsistent, and sometimes completely broken across devices. Here are 5 UI mistakes I made early in my Flutter journey and how I fixed them.

5 UI Mistakes I Made When Starting Out in Flutter (And What I Learned) When I started learning Flutter, I thought building UI was just about placing widgets on the screen. I was wrong. 🧵 #100DaysOfCode

There’s no “right” time. There’s no “perfect” time. There’s only right now. Start with what you have. Take one small step. Create that business idea. Apply for that opportunity. Learn that skill you’ve been putting off. Just start. 🚀

This build helped me sharpen: • Navigation between multiple screens • Using list helpers like .where() + .any() + .indexWhere() • Passing data across screens (no state mgmt yet keeping it simple 😄) ⁠ Excited to keep pushing myself and leveling up one project at a time 💪

✅ Just wrapped up a new Flutter project : Savorly 🍽️🚀 It’s a food recipe app where you can: • Browse categories & meals • Filter lactose-free / vegetarian / vegan options • View ingredients + preparation steps • Save favorites ❤️

Took a short break from Twitter to clear some offline tasks and focus on a few projects I had pending. Now I’m back, refreshed, recharged, and ready to start sharing what I’ve been working on.

So far: 👉 Category Screen — shows food categories 👉 Meals Screen — lists meals under each category Still a work in progress, but it’s coming together nicely.

Today, I kicked off a new Flutter project — a food recipe app called Savorly 🍽️ Goal: Level up my Flutter skills. I’m experimenting with approaches like namedRoute to structure navigation cleanly. #Flutter #Savorly #MobileDev #FlutterDev #LearningInPublic

Every big win begins with one small step… Just start 🎯

Sometimes the problem isn’t a big architectural issue. It’s one tiny, sneaky typo. Truth is, every dev has that bug. The one that humbles you. But it’s also the one that sharpens you. Be honest… how many hours have you lost to a silly error before? 😂

One small mistake. Hours of pain. When I fixed it, the build succeeded in seconds. And I just sat there… half relieved, half laughing at myself. Here’s the thing: That day taught me something deeper than fixing bugs. It taught me humility.

At this point, I started doubting everything. Is it Flutter? My code? My destiny? Hours later, I finally caught it. 👉 A tiny misspelling in my class name. Yup. That was it. Two conflicting names silently fighting each other behind the scenes.

I was using the freezed package and i was so sure i followed the docs correctly. I checked every line. I moved abstract around. I deleted. Rebuilt. Ran build_runner again. Same error. No mercy 😅