Sólides

Opening the app for the first time

The moment you install Sólides and tap the icon, you are not looking at a simple clock-in tool. The first screen asks for your company's login credentials — not a personal email. This is a business-first application. The company provides a specific domain or code. Without that, the app shows nothing useful. This is the first reality check: Sólides is useless outside a registered organization. Once inside, the dashboard loads with a news feed at the top. Below that, a large button labeled "Registrar Ponto" (Clock In) dominates the view. The app immediately asks for camera access. This is not optional. The facial recognition system is the primary clock-in method. If you deny camera permissions, the app warns you that you cannot record your time. The geolocation option appears as a secondary method, but the interface pushes facial recognition as the default. This setup takes about 90 seconds for a first-time user, assuming they have their company credentials ready.

The onboarding flow does not include a tutorial. There is no "welcome" walkthrough. The user is dropped into the live interface with no explanation of what the icons mean. The news feed shows company announcements, but these are empty for new users until the company populates them. The clock-in button is the only clearly labeled action. Tapping it triggers the camera. The app processes the face and records the timestamp. That is the entire onboarding experience. This directness is both a strength and a weakness. It gets the user to the core function fast, but it leaves the advanced features — skills matrix, PDI creation, performance reviews — completely hidden behind menus that are not obvious to a new user.

How facial recognition and skill tracking work together

Facial recognition is not just for clocking in. The system stores every facial scan with a timestamp and a geolocation tag (if enabled). This data feeds into the time reports module. Managers can see who clocked in, when, and from where. But the more interesting connection is with the skills matrix. The app does not explicitly link clock-in data to skill development, but the underlying platform does. When an employee consistently clocks in late, the system flags this in the performance evaluation module. The manager can then create an Individual Development Plan (PDI) that includes punctuality as a goal. The PDI tracks progress through subsequent clock-in records. This creates a loop: attendance data drives performance feedback, which drives skill development. The Play Store description mentions these features separately, but it never explains that they are connected. A manager who only uses the clock-in feature misses the behavioral intelligence layer that the platform offers.

This connection is not automatic. The manager must manually create the PDI and link it to the attendance data. The app does not generate recommendations. It provides the data, but the human still has to interpret it. This is a common frustration reported by users: the app collects a lot of data but does not tell you what to do with it. One YouTube tutorial shows a manager spending 20 minutes setting up a single PDI because the interface requires multiple clicks to link the right metrics. The data is there, but the workflow is not streamlined.

What the changelog actually says

The current version changelog on Google Play states: "Performance and stability improvements, adjustments and time sheet signing. - Internal fixes and improvements." This is the third consecutive update with almost identical wording. The previous versions also listed "performance improvements" and "bug fixes" without any detail. The developer has not published specific changes since the major update that merged the Ponto and Gestão apps into the Super App. Users on Reclame Aqui have noted that the updates often break existing functionality. One complaint from July 2025 describes a bug where the app would not load the clock-in screen after an update. The fix required reinstalling the app. The vague changelog does not inspire confidence. It signals that the developer is either not tracking changes carefully or does not want to communicate them. For a business app that handles payroll data, this lack of transparency is a real concern.

The app version 3.41.2 is the latest as of this writing. APKPure lists the download size as 70.7 MB. The app requires Android 7.0 or higher. These are the only concrete technical details available. The developer has not published a detailed version history anywhere. The help center only provides generic setup guides, not release notes. If a company relies on this app for payroll compliance, the vague updates are a liability. You cannot audit what changed if the developer does not tell you.

The permission model and what it actually does

Sólides requests camera access, location access, and storage permissions. The camera is mandatory for facial recognition clock-in. The location permission is optional but recommended for geolocation tracking. The storage permission is used for caching reports and news feed images. These are standard for a time-tracking app. However, the app also collects "personal information" and "other data" per the Play Store data safety section. The developer states that data is encrypted in transit but cannot be deleted by the user. This is a critical detail: once your data is in the system, you cannot remove it. The privacy policy on the Sólides website clarifies that users can request deletion via email, but the app itself does not provide a delete option. This is a compliance risk for companies operating under LGPD (Brazil's GDPR equivalent). The app collects location data even when the app is in the background, according to some user reports. The permission request does not explicitly state this. The user grants "approximate location" and "precise location" permissions, but the app does not explain that it will continue tracking location after the user closes the app. This is a documented complaint on Reclame Aqui.