Shipaton: Do0ne Build Journal #2 - Using Do0ne in Practice & Custom Loading Screen with Lottie Icons

Day 2 Begins

Today, I started the second day of work at a 24-hour café with a cup of coffee. I continued the project by actually using Do0ne, the app I built with basic functionality on Day 1.

For Shipaton, I set the goal as “Launching the Do0ne app.” To reach this goal, I registered and completed the necessary tasks one by one, which also allowed me to validate Do0ne’s workflow from a real user’s perspective.

Benefits from Real Usage

Previously, when organizing app development tasks, I used to write down everything, assign priorities, and schedule them by date—a process that often felt cumbersome and tiring.

With Do0ne, the experience was different:

• I only needed to register one immediate task at a time, making it much easier to stay focused.
• Having the current task displayed prominently at the center of the screen gave me extra motivation to finish it quickly.
• Since I had chosen this task as the most important one, I could work on it without worrying about all the other pending tasks, which gave me peace of mind.

This approach felt refreshingly different from conventional to-do apps.

FlutterFlow: Custom Loading Screen with Lottie Icons

Previous Approach
FlutterFlow has a default loading indicator, but it only shows an animation on the clicked button itself. This made it hard to tell whether the app was truly loading, and visually it wasn’t very appealing.

What I Wanted
I wanted a large loading icon centered on the screen, styled with a more polished animation that fit the overall design of the app.

Solution

1. Downloaded a preferred loading animation from LottieFiles
2. Created a Custom Dialog in FlutterFlow and inserted the loading component.
3. Configured the Action Block to call the Custom Dialog with Non-Dismissible (to prevent it from closing by tapping the screen) and Non-Blocking (to allow subsequent actions to run) options enabled.
4. The logic was: display the loading component, run the process, and then close the loading component afterward.

Summary

On Day 2, I tested Do0ne in real usage and confirmed its core strength: helping me focus on one task at a time. I also implemented a custom loading screen with Lottie icons, which improved the app’s UI beyond the default FlutterFlow loader. By the end of the day, I could clearly see Do0ne evolving into a more practical tool for real use.

Fun Element

So far, I’ve completed 7 tasks. Compared to predefining dozens or even hundreds of tasks in advance, this approach feels much lighter and more motivating. I’m curious to see how many tasks will have been completed by the time Do0ne is fully launched, and I’m excited to discover just how much I will have accomplished.