In a mobile app, the relationship of screens to each other takes precedence over their individual appearance. I build the Figma interface on this structure by determining registration, first use and basic task flows. I also consider the moments when the user encounters an empty result, error or permission request as part of the design.
Scope of the study
- User flows and screen priorities
- Interface and components suitable for the platform
- Empty, loading, error and success statuses
Let's define the limit of the first version together
- We define together the basic task that the user will complete in the application, the registration and first use flow. The number of screens appears as a result of this flow.
- While maintaining the common visual language for iOS and Android, we evaluate platform behaviors such as fallbacks, permissions, and system components separately.
- We write the design states of modules such as membership, payment or notification in the scope list; We separate software and third-party integrations separately.
What should be clear when handing over to the developer?
- Besides the basic screens, we schedule empty list, connection error, installation and transaction completed states.
- We specify the different states of the components, the placement when the text is extended, and the touch areas in the design file.
- Clickable prototype describes the flow; It is not a running application. The team responsible for coding, testing, and store release is determined at the outset.
Design process
Preparation, design and delivery
I clarify the first release target of the product and set up the basic flow with wireframe. After the visual design and prototype, I transfer it to the developer with its status.
Deliveries
- Editable Figma screens
- Prototype of basic flows
- Component and developer delivery notes
Frequently asked questions
Are you uploading the app to the store?
This service includes design delivery. Development, store accounts, and the release process are separate responsibilities; Who will manage the project is determined at the beginning.
How is the scope of the proposal determined?
In addition to the number of screens, user roles, platform differences, and custom interactions change the budget.
Can I get design support without completely changing my existing application?
Yes. First, we review the problematic flow, existing screens, and user feedback, if any. A specific flow, such as registration, search, or payment, can be treated as a separate job. It is not always necessary to redesign the entire product.
What should I submit for a mobile app design proposal?
Share the purpose of the application, target user, work to be done in the first release, and target platforms. Screenshots of existing product and flows you want to change are also helpful. We create a comparable proposal by writing the design, software and publishing responsibilities separately.
Let's determine the scope of the project together
In addition to the number of screens, user roles, platform differences, and custom interactions change the budget.
The startup's first mobile application interface
For mobile application interface design, the initial user task, registration need and interrupted operations are planned together. The answer to the question of how to design the first product for a startup is to make the basic flow testable instead of adding all the features at once.
Apply the checklist in the Design mistakes made by early stage startups guide to your product. If a demo is required for the investor call, we can scope product prototype design separately from working application development.
