Web and mobile app development that fits the routine of the people who use it
For companies that need to bring processes, information and customer service to the browser, to the phone or to both. Solvers starts from the routine of the people who will use the app, chooses the right format with you, connects it to your company’s systems and follows its evolution.
Prefer email? Write to contato@solvers.com.br.
The right format depends on who uses it and where
A team at the office, a professional in the field and a customer following a delivery may need different kinds of access. That is why the choice does not start with the trendy technology, but with who needs the information, where they will use it and which process needs support.
- Web application. Accessed through the browser, it adapts to different screen sizes. It can be a good choice when the work depends on a connection and users need to access information on computers and phones without installing anything.
- Mobile app. Useful when the experience needs to take advantage of device features, such as biometric authentication or file sharing. It also makes access easier through the app store and adapts to the mobile routine.
- Both, connected. A web portal and an app can share the same information, each in the context where it is most useful.
Offline use should not be assumed: if it is needed, it must be a project requirement from the start.
What goes into an app project
- Understanding the process, the data needed, the responsibilities and the expected results, before the screens.
- Choosing between web, mobile or both, and defining the requirements that change the project, such as offline use and device features.
- Integration with the systems and external services the operation depends on, with the behavior of each integration defined.
- Access and information protection: permissions, configuration and features such as two-factor authentication and biometrics, when appropriate.
- Publishing on Google Play and the App Store, when applicable, with each party’s responsibilities agreed.
- A scoped first delivery, with priorities and validation criteria, and the next steps defined with the client.
- Follow-up, fixes and maintenance, according to the agreed scope and terms.
From the routine of the people who use it to the app’s evolution
A useful app needs to fit the work of the people who use it. That is why the process comes before the screens.
- 01
Understand the routine
Who will use it, where, with what information and responsibilities, and what result the company expects.
- 02
Choose the format
A web application, a mobile app or both, considering connectivity, device features, distribution and maintenance.
- 03
Define the first delivery
A scoped delivery, with clear priorities and validation criteria.
- 04
Develop and integrate
Screens, rules, access and the integrations with the systems the operation depends on.
- 05
Validate with users
The client’s team clarifies the rules and evaluates whether the flow meets the operation’s needs.
- 06
Publish
In the browser and, when applicable, on Google Play and the App Store, with each party’s responsibilities agreed.
- 07
Evolve
Follow-up, fixes and new steps, according to the needs identified and what was agreed.
My Solvers: a connected web portal and app
My Solvers, developed by Solvers, brings together project information, documents, billing and support. It can be accessed on the web and through an app for Android and iOS. On the phone, the app presents the portal in a structure designed for the device, with features such as file sharing and biometric access to the session, when that option is enabled and available.
The solution talks to external services: Azure DevOps for project information, Clicksign for document signing, Banco Inter for financial processes and Focus NFe for issuing service invoices, according to the applicable features and configuration. Learn more about systems integration.
When a piece of information changes, the system records an event, a notice to the steps that need to know about it, and later processing takes care of routing it. Access includes two-factor authentication.
These choices meet the needs of My Solvers; other projects may call for different solutions.
Questions about app development
Do I need a mobile app or a web system?
It depends on who will use it, where they will use it and which process needs support. A web application is accessed through the browser and adapts to different screens, without installation. An app can be useful when the experience needs to take advantage of device features. In many cases, combining the two makes sense.
Does the app work offline?
Offline use should not be assumed. If it is needed, it must be a project requirement, defined from the start and included in the solution.
Does Solvers publish the app on Google Play and the App Store?
When the app is distributed through the stores, we agree on who is responsible for the account, the submission, the required information, the updates and following the review. The split depends on whose name the app will be published under, the access available and the contract. Approval is up to the stores themselves and should not be taken for granted.
Can the app connect to the systems the company already uses?
It can, when the operation needs it. My Solvers, for example, has integrations with Azure DevOps, Clicksign, Banco Inter and Focus NFe, each serving a product need and subject to the applicable configuration. Each integration has its own behavior, which needs to be defined in the project.
What about access security?
Access can rely on features such as two-factor authentication and, on the phone, biometrics, when the device offers it and the user enables it. These mechanisms are part of a security approach that also depends on permissions, configuration and care throughout development. No single feature eliminates every risk.
What does it mean for an application to work with events?
An event is a record that something relevant happened in the system. Instead of each step depending on a rigid sequence, other components react to the event and do their part. The design also needs to account for monitoring and for handling failures and repetitions.
What happens after delivery?
Follow-up, fixes, maintenance and evolution follow the scope and terms agreed in each project. Evolution depends on the needs identified with the people who use the app.
Learn more
Blog articles in Portuguese:
What routine does your app need to support?
Tell us who will use it, where, what information needs to be at hand and which systems the app needs to talk to. From there, we assess the format and where to start together.
Talk about your app →Or write to contato@solvers.com.br.