adminBiometric Attendance Application (fingerprint and/or facial recognition)
Objective: Develop a mobile application (iOS and Android) for recording attendance, check-ins and outs, incidents, and authorizations.
1.Check-in and out Registration:
Attendance recording.
Check-in and check-out times.
Lunch break registration with notifications (e.g., 10 minutes before lunch break starts and 10 minutes before it ends).
Short break registration.
Data storage in a database.
Access to a server and database via a web service.
2.User Profile:
Registration of personal data (name, department, supervisor, position, group, etc.).
User signature. To replace their signature, the employee can take a photo of their institutional ID and upload it to a repository, linking the photo URL to the employee in the database.
Display of the institutional regulations with confirmation of reading (acceptance check).
3.Notifications, Authorizations, and Incidents:
Sending notifications by Human Resources (HR) and other departments.
Authorization of permits, medical appointments, etc., from the mobile application by designated persons (HR and direct supervisors).
Incident reporting with details, evidence photo taken with the cell phone camera, and cell phone geolocation.
4.Points of Interest and Geolocation:
Registration of multiple work points per user (e.g., works at different branches and can check in and out at those assigned points to be considered valid; if done at another location, it will be marked as invalid and identifiable in the database).
Verification of check-ins and check-outs from any location with geolocation.
Geolocation with timestamp.
Assignment of entry and exit schedules for each day of the week for each employee to detect if the check-in was made within or outside the assigned schedule for that day.
If a permit, medical appointment, or authorized absence was requested, the application will not allow the check-in and will inform the user that they cannot check-in because the day is already marked as a permitted absence.
5.Cross-Platform:
The application must be available for Android and iOS.
6.Biometrics and Security:
Integration of biometrics (fingerprint and/or facial recognition) for signatures and security.
Biometric comparison with data stored in the client’s remote infrastructure.
Necessary Modules:
1.Login:
User authentication by username, password, and biometrics (fingerprint and/or face).
Reading of Privacy Notice and Terms and Conditions.
2.User Profile:
Viewing and updating personal data.
Reading and signing the institutional regulations.
3.Check-in and Check-out Registration:
Registration of check-ins, check-outs, and lunch breaks.
Reminder notifications before lunch break and its end.
Record history.
4.Notifications:
Sending notifications by the company to individuals or specific groups.
Receiving and reading notifications by users.
5.Authorizations and Incidents:
Requesting and approving authorizations (permits, absences, medical appointments, etc.).
Incident reporting with photo and geolocation.
6.Points of Interest or Locations:
Registration and consultation of frequent locations.
7.Settings:
Personalized configuration options for the user.
Notification and alert preferences.
8.History and Reports:
Viewing reports of:
Attendance
Check-ins and check-outs
Authorizations
Whether they checked in at the indicated location or not.
Reports should be filterable by all employee data, hours, and dates.
All reports should be exportable to CSV or XLS (Excel).
Testing and QA:
Testing and quality assurance (QA) will be a crucial part of this project. We expect unit tests to validate code logic, integration tests to ensure different modules work well together, functional tests to verify each feature works as expected, and regression tests to ensure new updates do not break existing functionalities. Usability tests will also be conducted to ensure an intuitive and smooth user experience.
Deliverables:
Well-commented source code.
Configuration files and documentation explaining their purpose.
Compiled packages for Android and iOS.
Technical Considerations:
Biometrics will be managed from the client’s infrastructure and compared using OpenCV or third-party services like Auth0, Okta, or Facetec.
It must support multiple companies, as each company will have its own structure of employees, positions, etc.
Important Note: The backend responsible for biometric comparison will be developed by another team. The application must connect to this backend via APIs.
Proposed Services and Technologies:
For notifications and alerts: Use third-party services.
We Provide:
Database (we will structure and create the necessary tables for the app that do not exist in the current structure).
Backend for current functions in the desktop panel that could be used in the app, and web services.
Infrastructure
Posted On: July 10, 2024 03:20 UTC
Category: Mobile App Development
Skills:Flutter, Smartphone, Android, iOS, Mobile App Development
Country: Mexico
click to apply
Powered by WPeMatico
