When working with a freelance mobile application designer, do not define the end of the delivery as just sharing the Figma file. The development team needs to understand user flows, component states, and unexpected conditions. Mobile app design is not the same delivery as working application software; The connection of the two must be planned.
Make platform and device decision early
The same brand language can be used for iOS and Android; However, platform expectations and technical components may differ. Determine as a team which device sizes and orientations will be supported. Which development approach the design is transferred to may also affect implementation boundaries.
Don't forget permissions and connection states
It is also normal for the user to reject a feature that requests camera or location permission. Design what happens when the internet goes down, a transaction times out, or no data arrives. Especially in critical flows such as registration and payment, the user should be clearly informed whether the transaction has been completed or not.
Have the handover meeting in a real scenario
Walk the path a user would take from start to results screen. Which information comes from where, which field is mandatory, is the data protected upon return? Record any unclear decisions alongside the file. Don't assume that the migration that worked in the prototype will automatically work in the real application.
Design control after development
In the implemented version, text overflow, keyboard behavior, loading state, and visual dimensions are comparable to the design. The scope of this check and the number of rounds to be carried out should be part of the offer. There is a distinction between a request for a new product feature and a correction in the implementation of an existing design.
screen states guide can be used as a starter checklist when working on mobile app design with Istanbul-based or remote teams.
Frequently asked questions
At what stage should we transfer the mobile application design to the developer?
Once the main flows and critical screen situations are clear enough, a controlled handover can be performed. Components, behavior notes and open decisions should be shared together; A checkpoint should be reserved for developer questions.
Is the application's behavior when disconnected also by design?
What the user will see and what actions he can perform falls within the scope of design. How the data will be stored technically should be decided together with the development team. The error message and retry flow should not be left ambiguous.
