Throughout this project, I faced a few challenges that became valuable learning opportunities. One of the biggest lessons was understanding the importance of following each design phase in the right sequence.

After completing the problem mapping and documentation, I rushed into designing the screens, skipping the user flow. Later, I realized that several edge cases hadn’t been considered, such as scenarios where no rooms are found or when a user inputs an invalid phone number. This made it clear that user flows are essential to identify all possible variables early on, ensuring a smoother and more complete user experience.

I also deepened my use of Figma features like components, variables, and auto layout, which allowed me to build a flexible and scalable UI system. These tools were especially useful in maintaining consistency across repeated elements like status tags, room cards, and buttons.

Another key lesson was the importance of starting with foundational components before diving into screen design. If I were to begin this project again, I would first create a library of reusable elements, such as buttons, input fields, and layout blocks using Figma’s component system and auto layout. By initially skipping this step, I ended up duplicating effort and making updates manually across multiple screens. This helped me realize how crucial it is to build flexible, well-structured components early on, so that future adjustments can be made easily and consistently throughout the UI.