I would definitely plan the app before building it. A simple structure created early usually prevents a lot of redesign and development work later.
A practical process is:
-
Define the users and their main goals.
-
Map the navigation and essential user journeys.
-
Prepare the copy in a shared document.
-
Create low-fidelity wireframes in Figma.
-
Convert the key screens into a clickable prototype.
-
Test the prototype with representative users.
-
Finalize the visual design before development begins.
InDesign and PDFs can communicate an initial visual idea, but Figma is usually better for mobile app development because it supports reusable components, interactive prototypes, comments, screen states, and developer handoff.
When working with a mobile app development company such as AppVerticals, the process normally progresses from requirements and user flows to wireframes, UI design, prototyping, and engineering. This makes it easier to identify unclear navigation, missing content, and technical requirements before coding begins.
For an event app, I would prototype the home screen, schedule, session details, speakers, venue information, notifications, and attendee-support flow first. Then check whether users can reach the most important information within two or three taps.
------------------------------
Saad Uddin
SalesforceGenericAccountUnited States
------------------------------