Hi @ANDRÉ LOBO 

I would start with a simple approach and add more features only if they're really needed.

A basic solution could have an Employee table and a Time Entry table to store clock-in and clock-out times. Then create a screen where the user can easily punch in and punch out with a single button.

If you need extra security later, you can add things like GPS location, photo capture, or manager approval for edited time entries.

Keeping the first version simple makes it much easier to maintain and improve as new requirements come up.

Hope this helps!

Regards,

Manish Jawla

Hi @ANDRÉ LOBO ,

Here are some suggestions for this project:

Mobile Layer:

For the employee: standard time-clocking (including geolocation, employee photo capture—though managers can disable this requirement—and timestamping based on the server clock to prevent mobile device time manipulation) as well as manual time entry (requiring a justification, the option to attach a photo and/or document, and manager approval).

Web Layer:

For the manager: monitoring employee attendance; approving or rejecting manual time entries; generating monthly reports; and adjusting configuration settings, such as requiring an employee photo during clock-in/out.

Security Measures:

On mobile: check if developer mode or root access is enabled (if so, the app should flag the use of these features); detect the use of VPNs or "Fake GPS" apps and log a note regarding their use in the employee's time record.

I created a brief requirements document with the help of AI, which is attached here for your review. Since you mentioned this in Portuguese, I prepared the document in Brazilian Portuguese (PT-BR).

Best regards,
Edson Marques

For the front end, you can put your requirements in Stitch, for example, and have some mockups that help you get a clearer idea of what screens you need.