ASPSAUDE

Opening the app for the first time

Install ASPSAUDE on an Android phone and the first screen shows a login field. There is no guest mode and no demo account. The app expects a real community health agent credential issued by a Brazilian municipality. Once logged in, the main dashboard displays three large buttons: Individual Registration, Family Records, and Schedule Home Visit. The interface is entirely in Portuguese, which matches the developer's location in Araçatuba, São Paulo. The design is functional, not polished. Buttons are large enough for field use, and the color scheme uses green and white, typical of Brazilian public health tools.

The onboarding flow does not include a tutorial. New users are expected to already know the basic workflow. The app assumes the agent has been trained separately. Tapping Individual Registration opens a form with fields for name, CPF (Brazilian national ID), birth date, and address. The form saves data locally and syncs when a network connection is available. The Family Records section lets agents group registered individuals into households. This grouping is essential because home visits are scheduled per family, not per individual.

How registration and scheduling actually work together

The individual registration and home visit scheduling features are not independent. When an agent registers a new person, that person does not automatically appear in the scheduling list. The agent must manually link the registered individual to a family record first. Only after linking can the agent select that person for a home visit. This two-step process creates a clear point of failure. If the agent forgets to link the individual to a family, the scheduling screen shows the person as unavailable. The changelog for the current version explicitly fixes a problem that occurred when selecting a citizen for a home visit. That fix likely addressed cases where the linking step failed silently, causing the selection screen to crash or show an empty list.

This workflow reveals a design trade-off. The app separates registration from scheduling to keep data organized, but the separation adds extra taps and increases the chance of error. A more streamlined app might combine these steps into a single flow. ASPSAUDE does not. The agent must remember to complete the linking step before moving to scheduling. In practice, this means agents develop a routine: register, link, then schedule. Missing any step breaks the chain. The changelog fix suggests that the selection screen previously did not handle unlinked individuals gracefully, which would have frustrated agents during fieldwork.

Performance in the field

ASPSAUDE does not display ads, which is a relief for a tool used in professional settings. There are no pop-ups, no banner ads, and no interstitial screens. The app runs offline for most operations, which is critical because many Brazilian rural areas lack consistent mobile data. Registration forms and family records are stored locally. Scheduling also works offline. The app only requires an internet connection when syncing data to a central server, presumably managed by the municipal health department.

Bugs are not publicly documented, but the existence of a changelog fix indicates at least one known issue was present. The fix addresses a problem with citizen selection for home visits. That problem could have caused the app to crash or freeze when an agent tried to assign a visit. The fix is specific and technical, not a generic "performance improvements" line. This suggests the developer is responsive to actual field feedback. The app does not have a visible feedback mechanism within the interface, so agents likely report issues through municipal health coordinators, who then contact the developer.

The app's performance is adequate for its purpose. It does not feel slow, but it also does not feel fast. Scrolling through a long list of registered individuals can take a second or two to render. The app does not use animations or transitions, which keeps it lightweight. The file size is not listed on the Play Store, but the app's simplicity suggests it is under 20 MB. It runs on most Android devices from the last five years without requiring high-end hardware.

The permission that makes it work

ASPSAUDE requires access to the device's storage. This permission is necessary because the app saves registration data, family records, and scheduling information locally. Without storage access, the app cannot function offline. The permission request appears during installation, and the app does not proceed without it. There is no option to use the app in a read-only mode or with cloud-only storage. The storage permission is the only critical permission requested. The app does not ask for location, camera, microphone, or contacts. This minimal permission set is a positive sign for privacy. The app also does not collect or share any data with third parties, according to the Play Store data safety section. The storage permission is used solely for local database files, not for accessing personal photos or documents. The app creates its own folder in the internal storage and does not scan other directories.