Saltar al contenido

Plantillas de apps móviles de Utilities & Tools

A utility does one job, and the first screen should be that job. A scanner opens on the camera. A converter shows the input and the result together. Weather leads with today's number and the next few hours. A password tool leads with the list and a search field. If the user has to learn a tab bar before they get a result, the app is already larger than the job.

The second screen is the result they keep. A saved scan, a file, an export. Put share or save in the same corner every time. History is a simple list of past results, each row named and dated. Settings come last, behind one icon, and they should not be required to get the first result.

Ask for a permission on your own screen before the system dialog, with the reason next to the button the user just tapped. A line such as scan a document, next to the camera button, is enough. Asking on first launch, before any tap, is how people deny access and never find the setting again.

These templates are small on purpose. A feed, a social tab, or a points balance turns a tool into a different product. If a new idea needs its own tab, it is probably a separate app. Start from the template that already does the job, and delete screens instead of adding a dashboard above the tool.

Dudas, resueltas. Todo lo que necesitas saber antes de empezar.

What belongs on the first screen?
The job. A camera for a scanner or a QR reader, two fields for a converter or a calculator, today's conditions for weather, the list for passwords. A marketing hero above the tool pushes the job down, and people notice.
How should results be saved?
A list the user can reopen, each row named and dated, with share or export on the result itself. A scan that disappears when the app closes is a demo. Weather is the exception: the result is today, and history is earlier days, not a file.
When should the app ask for camera or file access?
After the user taps the action that needs it, with one line on your screen that says why. Then the system dialog. Asking on first launch, before any tap, leads people to deny the permission and skip the tool.
How do I keep a utility from turning into a suite?
One primary object. A document, a conversion, a forecast, or a login. If the next idea needs its own tab, it is likely a different app. Start from the matching template and delete extra screens instead of adding a home dashboard.

¿Alguna otra duda? Escríbenos a support@sleek.design.

Tu app, diseñada esta misma noche.

Empieza con una frase. Sleek diseña todas las pantallas con un solo estilo.

Empieza gratis. Sin tarjeta de crédito. Usado por más de 60.000 creadores de apps.