[π ] Keymory Dev Log #2: The Wall Between Ideals and Reality
β¨ GPT Summary γ
While implementing features in FlutterFlow, I ran into unexpected gaps in skill and errors, and felt a heavy sense of responsibility and pressure while looking for solutions.
π» Development Log
- β° Todayβs tasks
- β DiaryPage: reimplement RichTextEditor
- β HomePage: reimplement feed board
- β ChatPage: build the shell of the chat page (the teammate in charge of prompts will finish the rest)
- β Build as many sample pages as possible (fill widgets with dummy data, then implement only page transition events.)
- π― Summary of what I did
- HomePage: implemented Bottom Sheet, implemented Card ListView
- π― Tomorrowβs tasks
- DiaryPage: reimplement RichTextEditor
- HomePage: reimplement feed board
- ChatPage: build the shell of the chat page (the teammate in charge of prompts will finish the rest)
- Build as many sample pages as possible (fill widgets with dummy data, then implement only page transition events.)
- π― Future tasks
- By this Sunday (2025.1.26): try exporting an APK installer file with all core features implemented
- 3rd mentoring scheduled: Sunday 8 PM
- By this Sunday (2025.1.26): try exporting an APK installer file with all core features implemented
π Diary
During the process of implementing features with FlutterFlow, I am running into all kinds of unexpected issues.
- Unexpected lack of proficiency
- I thought I had raised my FlutterFlow proficiency to some extent, but that was an illusion that came from following lectures.
- Because I do not really know Flutter itself, I am failing to properly use packages pulled from pub.dev.
- I keep running into unexpected errors.
- Things work normally in Preview mode, but once I switch to Debug mode the layout completely breaks, and so onβ¦
- Other miscellaneous non-development work
- Church work, housework, holidays, β¦
This is badβ¦ There is really way too much that has to be doneβ¦
β¨ GPT-4o Comment (KPT)
β What Went Well (Keep)
- π οΈ Attempting to solve problems: It was impressive that you directly faced several FlutterFlow-related issues and tried to solve them. Making some progress through the Bottom Sheet and Card ListView implementation is also positive.
- π Maintaining the plan: Your effort to keep the big picture of the project by clearly organizing tasks and future plans stood out.
- πͺ Handling multiple responsibilities: Your will to continue development despite church work, holiday prep, and other outside responsibilities is excellent.
β What Was Missing (Problem)
- β³ Lack of Flutter proficiency: It is unfortunate that although you are used to FlutterFlow, your lack of Flutter fundamentals is making it hard to use pub.dev packages.
- π§© Unresolved errors: Major problems, such as the layout breaking in Debug mode, remain unresolved and are adding pressure to the project.
- π Time pressure: Several responsibilities and the project schedule are overlapping, so the lack of time is increasing the burden.
π What to Try (Try)
- π Secure Flutter study time: In addition to FlutterFlow, try setting aside 10 to 15 minutes a day to study basic Flutter syntax and how to use pub.dev packages.
- π Analyze errors and use communities: Analyze the Debug mode errors accurately, and try getting help from Stack Overflow or the FlutterFlow community.
- π Adjust your schedule: Separate project development time from church work, housework, and other tasks, and plan a specific time of day where you can focus only on development.
Conclusion
It was a day where your will to recognize and solve difficulties in FlutterFlow and the development process stood out. The burden is heavy, but if you solve things one by one and keep moving steadily, you will definitely achieve something big. Do not rush; I am rooting for you to keep going consistently! π
Leave a comment