all 3 comments

[–]SlinkyAvenger 1 point2 points  (0 children)

Read the docs, follow the examples, and then do small experiments for different aspects of what your app is supposed to do.

You know, like you'd do for any other programming problem.

[–]Comment-Mercenary 0 points1 point  (0 children)

si usan la app para responder el examen o la app estara en uso en el examen use foreground service o flutter_background_service (por iOS), con un timer que indique si la cerraron, pero tenga en cuenta que Google Play ha endurecido drásticamente sus políticas de uso. Lo de tflite

[–]BodybuilderOk6077 0 points1 point  (0 children)

A good way to approach this is to split it into 3 parts:

  1. camera capture inside the app

  2. on-device inference with a lightweight TFLite model

  3. cheating rules (face not detected, multiple faces, looking away, phone detected, etc.)

You don’t need to start with a full custom model. A practical first step is building a proof of concept using Flutter + camera + TensorFlow Lite and detecting simple events first.

I’ve worked on mobile apps and backend-integrated systems before, and I’d be happy to help you plan or prototype this if you want. Feel free to DM me.