biosoft plus

Opening the app for the first time

Opening the app for the first time presents a login screen. No guest mode exists. No demo data appears. The app requires a registered account with the BiosoftNext system. Without credentials, the screen remains locked. This is not a standalone app. It is a mobile frontend for an existing HR management system. The login screen asks for a username and password. Below that, there is no registration option. New users must be added through the web-based admin panel first. This creates a clear boundary: the app is an extension of the desktop HR system, not a standalone product. The app does not offer any offline functionality. Everything requires an active internet connection. Users cannot clock in or request leave without a network connection.

The login process itself is straightforward. Enter credentials, tap the login button, and the home screen appears. The home screen displays a dashboard. The dashboard shows key actions: clock in/out, request leave, request OT, and pending approvals. Each action is a tappable button. Tapping "Request Leave" opens a form with leave type, date range, and reason fields. Tapping "Request OT" opens a form for overtime hours and reason. The clock in/out button records the current time and location. The app uses the device's GPS to log the clock-in location. This is a common feature in attendance systems. It prevents fraudulent clock-ins from outside the workplace.

However, the login process is not always smooth. The app may fail to authenticate if the server is down. Users have reported that the app sometimes gets stuck on a loading screen during login. This suggests a network dependency. The app relies heavily on a stable internet connection. If the connection is poor, the login may fail or time out. The app does not provide clear feedback on network status. Users are left guessing whether the problem is on their end or the server. The app also does not support biometric login (fingerprint or face recognition). This is a notable omission for a modern HR app.

How time recording and leave requests work together

The time recording and leave request features are deeply linked. Every clock-in and clock-out event creates a timestamp. Those timestamps accumulate into a daily log. The leave request feature allows employees to request time off. When a leave request is approved, the system automatically adjusts the employee's attendance record. This ensures that the employee is not marked as absent on approved leave days. The integration is efficient. It reduces the need for manual adjustments. The business owner can see the entire attendance and leave history from a single dashboard.

However, this tight integration also creates a single point of failure. If the time recording data is incorrect, the leave data will also be incorrect. Users have reported discrepancies between the app and the web platform. For example, a leave request approved on the web may not appear in the app immediately. This delay can cause confusion. The employee may think their leave is still pending when it has already been approved. The app does not provide a sync status indicator. Users do not know when the data was last updated. This lack of transparency is a common complaint in HR apps. The changelog mentions "Minor bug fixes and improvements." This suggests that the developer is aware of issues. However, the changelog does not specify what was fixed. Users are left to discover the changes themselves.

Real-world performance and common issues

The app's performance varies depending on the network condition. On a stable Wi-Fi connection, the app loads quickly. The dashboard updates in real-time. Notifications arrive instantly. On mobile data, the performance degrades. The app may take several seconds to load the dashboard. Notifications may be delayed. In some cases, the app fails to load data entirely. The app shows a generic error message: "Network error. Please try again." This error gives no specific guidance. Users do not know if the problem is with their connection or the server. The app does not retry automatically. The user has to manually tap the retry button. This manual retry process is frustrating, especially for employees who need to clock in on time.

The app also has a significant file size. The APK is approximately 164.6 MB. This is large for a business app. It may take up considerable storage space on the device. Users with older devices or limited storage may find this problematic. The app does not offer a "lite" version or the ability to clear cache easily. The app also requires Android 7.0 or later. This excludes users with older devices. The developer has not announced any plans to reduce the file size or support older Android versions.

Permissions and technical requirements

The app requests several permissions on Android. These include full network access, control vibration, prevent device from sleeping, receive data from internet, and delete all app cache data. These permissions are typical for a business app that requires constant connectivity. The "prevent device from sleeping" permission ensures that the app can receive notifications even when the device is idle. This is important for real-time approval alerts. The "delete all app cache data" permission allows the app to clear temporary files. This can help resolve performance issues. However, clearing the cache also logs the user out. The user must log in again after clearing the cache. This is an inconvenience. The app does not provide a clear explanation of what each permission does. Users may be hesitant to grant these permissions without understanding their purpose.

The app is available on both Android and iOS. The minimum Android version is Android 7.0 (API 24). The iOS version requires iOS 15.6 or later. The app size varies between 27 MB and 164.6 MB depending on the version and architecture. The app is free to download. There are no in-app purchases listed. However, the app is only accessible to BiosoftNext customers. This means that the app itself is free, but the underlying service requires a paid subscription. This business model is common for B2B apps. Users should be aware that the app is not a standalone product. It is a companion to the BiosoftNext platform. The app is developed by an individual, Pongsiri Chanasri, based in Thailand. This is a small-scale operation compared to larger HR software providers.