The challenge:.To Build a user-friendly mobile form app with: .A splash screen on launch.User authentication (sign-up/login) .Field validation (users can’t proceed without completing each one).On submission: display all user input on a new screen and save it to the database.

Told a tech joke at work today! 😄 Boss asked me to push the door to shut it, and I asked if I should push to origin master or origin main.😂 .Do you get it😂?. By the way, I apologize for not updating you all on my BIP tweets. Would resume them soon😊. #GitHub #techjokes.

One screen at a time, the app’s feeling more polished. Next post: user form 📜🚀. #Flutter #Firebase #Dart #MobileDev #BuildingInPublic.

Here’s what I worked on:.✨ Added helper texts for smoother navigation (e.g. “Already have an account?”).🧼 Built custom reusable alert boxes for error/success feedback.🔁 Auto-redirects to Login after successful sign-up.🔐 Integrated Firebase Auth for both login & signup.

BIP 004 — Optimized Auth UX + Firebase 🔐.This week was all about refining the auth experience and connecting to Firebase.

📂 Code Now on GitHub:.I’ve pushed the full code so far on GitHub — feel free to check it out, drop a ⭐, or suggest improvements!.See you in the next post!.#Flutter #Dart #CleanCode #BuildingInPublic #MobileDev.

🔜What’s Next?.I’ll be connecting the auth screens to a database. Still deciding whether to go with:.Firebase (quick & easy ☁️).MySQL (for a more hands-on setup and learning experience 🛠️).Which do you feel I should roll with—and why? Please let me know in the comments! 👇😄.

📚 Lesson Learned.I discovered the power of the TabBar widget — it made switching between Login and Sign-Up views super smooth. One widget, clean navigation — love it!.

🧪 First Validation phase Done.The login and sign-up forms are wrapped in a Form widget, with field-specific validation logic. This ensures users can’t proceed with incomplete or invalid input.

♻️ Reusable Code.One of my goals was clean, reusable code. So, I made a custom input widget and pressable button used across Login & Sign-Up screens — now reusable app-wide. Now, anywhere user input and a button is needed across the app, I just call these widgets 🙂‍↔️

Happy new month everyone!✨. On today’s Building in Public (BIP 003), .I present 🧼 Clean Code & 🔒Auth Screens;.Here’s the progress on the Login & Sign-Up screens.

Lesson’s Learned:.Avoid putting complex logic directly inside MaterialApp.home. Turns out, it’s better to .use a separate widget or screen for such logic. Shout out to my boss for the save😄. See you in the next post! ✨.#Flutter #Dart #MobileDev #buildinginpublic.

Challenges faced:.At first, I handled the splash with a FutureBuilder directly in home: —seemed simple, right?😅 It worked but led to some really weird rebuild issues like my TextEditingControllers in other screens (e.gLogin screen) to keep getting disposed on every hot-reload.

📱 What is a Splash Screen?.It’s the first screen you see when an app launches — usually shown for a few seconds before loading the main UI.

Hello everyone ✨😄.Welcome to Building in Public(BIP 002) . I decided to use Flutter & dart, and here’s what I’ve built so far:. ✅ Splash Screen.✅ Login & Sign-up Screens (details coming tomorrow).

📱 What is a Splash Screen?.It’s the first screen you see when an app launches — usually shown for a few seconds before loading the main UI.

I’ll be pushing the code to GitHub and sharing updates along the way. Wish me luck! 🚀😊.Let’s go! 💻🔥.#BuildInPublic #DevJourney.

debugPrint("Hello, world!"); Lol 😅👋. I’ve officially decided to start building in public to take my tech journey more seriously. To kick things off, I’ll be sharing my process, struggles, and the lessons learnt while tackling a warm-up challenge from my boss at work.

Been a while. :)

Lecturer dey ask people what languages dem fit write code in . I con tell am Flutter and Dart. He now come announce to class say may we no de talk jibrish 💀😭💔💔. #flutterdev #dart.