JuniCare

The app opens to a login screen. No demo mode. No guest access. You need an account to proceed. Parents download this app to pair with a child's smart watch. The watch itself is the key. Without the watch, the app is just a login page. The setup process starts with scanning a QR code on the watch or its packaging. That QR code links the watch to the app. The app then asks for a series of permissions — location, camera, microphone, storage, phone state. All of them. The list runs long. ACCESS_COARSE_LOCATION, CAMERA, RECORD_AUDIO, READ_PHONE_STATE, WRITE_EXTERNAL_STORAGE. Eighteen permissions in total. The app wants full access to the device. That is the first reality check. This is not a lightweight utility.

The login itself is straightforward. Email and password. But the problems start after login. Multiple user reports describe the same issue: after reinstalling the app, the watch disappears from the account. All settings are gone. The parent signs in with the same admin email, but no watch is bound. The watch is still physically there. The app just does not see it. That is a core failure. The entire purpose of the app is to communicate with the watch. If the watch is not visible, the app is useless. This is not an edge case. It is a recurring complaint across multiple review platforms.

How location tracking and classroom mode interact in practice

The location tracking feature uses GPS and LBS (Location-Based Services) to show the child's real-time position. The watch transmits location data to the app. The parent can see the child on a map. That is the intended workflow. But there is a catch. Classroom Mode, when activated, limits the watch to showing time and sending SOS signals. The watch stops accepting calls and messages. It goes into a restricted state. The question is: does location tracking continue to work in Classroom Mode? The Play Store description does not say. The app's behavior is not documented. If the watch stops transmitting location data during Classroom Mode, the parent loses visibility during school hours. That is a significant gap. If the watch continues to transmit, then Classroom Mode is only a communication block, not a full lockdown. The difference matters for safety. A parent who wants to know their child's location during school hours needs that data. A parent who wants the child to focus without distractions might accept losing location data. The app does not clarify which behavior occurs.

This is where the original analysis sits. The interaction between these two features is not described anywhere in the official documentation. The Play Store page lists both features separately. It does not explain how they work together. User reports suggest that location accuracy is already a problem — the app has shown a watch's GPS location in a different state. That is a serious error. If Classroom Mode further degrades location reporting, the feature becomes unreliable for its core purpose. The combination of these two features creates a practical limitation: the parent must choose between communication and location visibility, but the app does not make that trade-off clear.

The real-world performance of the app based on user reports

The app has a 1.78-star rating on AppBrain based on 27 ratings. That is low. The complaints are consistent. Connectivity failures are the most common issue. The app shows the watch as offline even when the watch is connected to Wi-Fi. The parent sees the offline status and cannot send messages or make calls. The watch is actually online. The app just does not recognize it. That is a synchronization problem. The app and the watch are not maintaining a stable connection. The user report from Chrome-Stats puts it plainly: "The app constantly shows the watch offline. Even after connecting it to wifi. Just recently, it's showing the apps GPS location in another state!" That is two failures in one sentence — offline status and incorrect GPS data.

Another user report describes a more severe issue: "Got kicked out of the app and watch doesn't connect anymore. Both giving error message." The app forcibly logs the user out. The watch loses its binding. The parent cannot re-pair the watch without going through the full setup process again. That is a critical failure. It means the app is not stable enough to maintain a persistent session. For a parental control app, that is unacceptable. Parents need reliability. They need to know the app will work when they need it. The current state of the app does not inspire confidence.

The developer, Shenzhen AKQ Smart Device Co. Ltd, has been active since 2024. The app has over 100,000 installs. That is a large user base. The complaints are not from a small sample. They are from multiple sources — App Store reviews, Chrome-Stats, AppBrain. The pattern is clear. The app has fundamental stability issues. The version history shows frequent updates — 2.7.3, 2.8.0, 2.8.1, 2.8.3, 2.8.7, 2.9.1, 2.9.5, 2.9.6, 2.9.7, 2.9.8. That is a lot of updates in a short time. The changelog for 2.9.8 says "minor bug fixes and general improvements." That is the same generic phrasing used in many updates. The developer is fixing bugs, but the core issues — connectivity, location accuracy, session persistence — persist across versions.

One specific permission and what it actually does

The app requests the READ_PHONE_STATE permission. That permission allows the app to read the device's phone number, network information, and call status. The app does not make phone calls itself. The watch makes the calls. The app is just the controller. The READ_PHONE_STATE permission is likely used to identify the device and manage the connection with the watch. But the permission is broad. It gives the app access to sensitive data. The app also requests ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION. Those are used for the location tracking feature. The app encrypts data in transit, according to the Play Store data safety section. That is a positive detail. But the app does not share data with third parties, which is also positive. The data collection includes location, personal info, and two other categories. The app does not collect data on iOS, according to the developer. That is a discrepancy. The Android version collects data. The iOS version does not. That difference is worth noting.