From the first touch to the completed task.
Initial release, renewal and platform behavior
First release
A screen and flow plan with clear boundaries that focus on the main task of the product.
Renewal
Addressing a specific usage issue or visual language in the current application.
Developer submission
Platform behaviors, component states, and annotated design files.
Let's develop the design of your mobile product together
The user's attention and available space on the phone screen is limited. As Freelance mobile app designer Selçuk Aker, I handle initial use, navigation, and completion of the main task together. Instead of increasing the number of screens from the beginning, we determine what the product should do well in the first version.
We can work on a new application idea, the renewal of an existing product or the development of a single flow. At the first meeting, “how many screens?” Before the question, we talk about the basic function of the product. Technical scope on mobile application design service page; Here you can find the decision process and working with the designer.
Which streams should be included in the first release?
We determine the initial value the user will receive from the product. We associate the registration, first use, search, reservation or purchase flows with the product goal, whichever is required. Instead of putting every idea into the first version, we make priorities visible.
The number of screens is the result of the flow. Different user roles or situations can exist on the same screen. On the other hand, some steps can be solved in a single order. In the scope list, I also specify the necessary states as well as the main screens; I don't leave it as if it appeared later.
What do I cover in iOS and Android design?
Navigation and system behaviors
The behavior of return, permission request, keyboard and system components may vary by platform. We discuss the platform differences that the technical team will implement while maintaining the common brand language. Just putting each screen in different phone frames is not platform adaptation.
Readability and interactivity
Text length, touch areas, form errors and dense content demand attention on the small screen. It is necessary to offer the user a continuation path for a list with no content or an unsuccessful operation. In the design file, I explain in which situation these will be seen.
Prototype and development transfer
The clickable prototype is for evaluating flow and transitions. Mobile application design and software development are separate scopes. Works such as API, payment, notification and store publication should be planned by the relevant developer. We clarify the design delivery with the needs of this team.
You don't have to completely replace your existing application
If there is a single flow that users are having difficulty with, we can start there. Screenshots, support requests, and current metrics help understand the issue. If no data is available, I mark the evaluation as assumption; I do not give an unmeasured recovery rate.
Identifying the design elements and technical boundaries to be preserved keeps the scope of the renovation in check. The development team should discuss how the new design will work with the old version and whether it can be phased in.
How is the freelance mobile application design price determined?
Basic flows, different roles, platforms, screen states and available files are inputs to the proposal. Editing two screens of a ready-made product is not the same as designing the first version from scratch. We also specify the scope of the prototype and developer interviews from the beginning.
In your first message, share the purpose of the application, target user, priority tasks and the current product, if any. You do not need to have prepared a detailed technical specification; We can separate the missing points together. You can also refer to mobile app guides for decisions during the design process.
When the connection is lost or the operation is incomplete
Mobile experience is not just about successful transactions. Appropriate feedback is required for connection loss, denial of permission, or returning to the application at a later time. We determine through the flow which situations are truly necessary in each project.
For example, preserving the form filled out by the user and returning the form to the beginning creates different expectations. I clarify these decisions with the developer and explain them in the design file with the relevant screen and status.
Frequently asked questions in mobile interface design
Do you code the app and upload it to the store?
This page describes the mobile interface design service. Software development, testing, accounts, and store publication are separate responsibilities. If it will be carried out together, the relevant team and scope should be determined at the beginning.
Can I have a design made only for Android?
Yes. We can proceed by determining the target platform and the components the developer uses. If an iOS version is planned in the future, we will take this into account in design decisions.
If my application idea is not clear yet, can we start?
A limited preparatory effort can be planned first, clarifying the target user and the main task. It would not be right to determine the duration and price of all screens for a vague idea.
Can you refresh the registration-only screen of my current application?
Yes. We can also create a limited scope by reviewing validation, error and permission statuses associated with the record. I wouldn't evaluate a single screen without seeing the steps around it.
Can the prototype be tested with real users?
A prototype prepared in an appropriate scope can be used to evaluate specific tasks. Participants, method and test boundaries are planned separately; The prototype does not measure the performance of the real application.
What screen states are included in the delivery file?
According to the agreed flows, empty, loading, error, successful transaction and, if necessary, authorization statuses are prepared. The list is clarified during proposal and design evaluations, without assuming that it covers every possible situation.
Let's define the boundaries of your first version
Send your project to Selçuk Aker. Let's plan together the main mission of the application, design deliverables and the way of working with the developer.
What will the first user achieve?
Write the target platform and the main task of the application. Let's separate those that will be released in the first version and those that can be postponed later.
- The main task of the application and the target user
- iOS, Android and current screen information
- First release scope and software team
