APPLICATION DESIGN II FINAL PROJECT & E-PORTFOLIO
22.05.2025 - 05.06.2025 / Week 5 -Week 7
Emily Goh Jin Yee / 0357722 / Bachelor of Design (Honours) in Creative Media
Application Design I/ DST60504 / Section 01
Final Project & E-portfolio
TABLE OF CONTENTS
1. INSTRUCTIONS
2. TASKS
3. FEEDBACK
4. REFLECTION
INSTRUCTIONS
TASKS
FINAL PROJECT & E-PORTFOLIO
Task 4 was essentially a continuation and refinement of what we had done in Task 3. While the core structure remained similar, I took this opportunity to carefully review my previous work to identify any missing elements or inconsistencies. Based on that review, I made several improvements, particularly by enhancing the visual flow of the project. I added more animations to ensure a consistent and engaging user experience across different screens. These adjustments helped align the overall design with the intended user journey and made the interface feel more polished and interactive.
FINAL SUBMISSION
website link here
walkthrough video: https://www.youtube.com/watch?v=5ASw0geaCF4
FEEDBACK
no feedback given
WEEK 14
General Feedback
- submission on Week 15 Tuesday
Specific Feedback
- fixed firebase expire date
REFLECTION
Experience
Task 4 was a continuation of the work from Task 3, where I focused on refining the interactive components and improving the overall flow and consistency of the project in FlutterFlow. I revisited areas that needed improvement—such as animations, visibility conditions, and action logic—and made the necessary adjustments to ensure a smoother and more consistent user experience.
Throughout this task, I encountered several challenges, particularly with the delay in FlutterFlow’s publishing system. Even after clicking “Publish,” updates didn’t appear immediately on the live site, and in some cases, components became unresponsive. I tried using Test Mode to troubleshoot, but certain elements still didn’t load. This made testing and recording the final version frustrating, especially as time was running out. When it finally worked, I managed to record everything—but it was already past the deadline.
Looking back on the entire module, I’ve seen clear growth in how I approach interaction design. At the beginning, I was unfamiliar with FlutterFlow and had to rely on experimentation and documentation to understand how the platform worked. Over time, I became more confident with using its tools—from managing components to setting up conditional actions and dynamic screens. Each task built on the last, and Task 4 allowed me to apply what I’d learned in a more strategic and polished way. Although the technical issues were frustrating, the overall journey taught me how to handle complex logic, structure my workflow more efficiently, and think ahead when designing interactive features.
Observations
I observed that changes in FlutterFlow do not always reflect immediately when published, which can create confusion when testing for final submission. Some components also behaved differently between the editor, Test Mode, and the live published version. I realized that creating reusable components gave me more flexibility in troubleshooting layout and interaction issues, and helped keep things consistent. Timing and visibility conditions also played a big role in how smooth or buggy the interface felt, even with small changes.
Findings
This task taught me that interactive development is just as much about problem-solving and preparation as it is about design. I had to think carefully about how each component would behave, how to manage updates effectively, and how to adapt when tools don’t respond as expected. The experience also highlighted the importance of double-checking submission steps and allowing more time for testing when using cloud-based tools. Overall, this task—and the module as a whole—helped me build a stronger foundation in interactive design, while sharpening my technical thinking and planning skills.




Comments
Post a Comment