confusion-matrix-2023 / autofis-m3 Goto Github PK

Multiple instances of camera screen are added to navigation stack on switching tabs

Semaphores or similar concepts can be used to just perform imageProxy.close() directly and return from the analyze() function when the image is being captured or some other process is going on.

https://medium.com/cnk-tech/android-multi-language-support-6b2109fe7aea

https://stackoverflow.com/questions/4259128/how-can-i-create-a-multilingual-android-application

By default, the file upload starts as soon as the device is connected to any network. An option can be provided to the user to choose the file upload condition like Network.METERED, Network.CONNECTED, etc.

https://developer.android.com/topic/libraries/architecture/workmanager/how-to/define-work#retries_backoff

https://developer.android.com/training/notify-user/group

Make a separate branch "no-box".
In that branch:

1. Remove the imageAnalysis part.
2. Perform imageAnalysis on the cropped bitmap of the image which is received from imageCapture. Show loading progress dialog while the image is being processed.
3. Move to the next screen if a fish exists in the current image.
4. Else, show a message/toast/snackbar saying "fish not detected in the captured image, please retake the photo"

Onboarding screen and tutorial with audio and arrows (with multi-language support)
https://developer.android.com/training/tv/playback/onboarding

Optimization by using GPU delegate serialization

Images that are captured but not submitted remain in storage forever. This happens when image is not submitted on enter details screen.

Possible solutions:

1. Check for such images frequently either after fetching history or in the init block of history ViewModel and then delete all.
2. Show such images in a separate section similar to the pending uploads section. Clicking on those images will navigate the user to the enter-details/{uri} screen.

Lag when navigating from the camera screen to enter details screen

The cancel option below the submit button will delete the image from the storage.
Back button behavior (both on the navbar and the top bar) can be changed in such a way that the clicked image will be deleted first and then the nav stack will be popped.

It doesn't detect newer fish types. This would be a great issue to fix i might suggest have more contributors who could identify these issues for quickly. im am extremely sorry if anything i said came off as rude.

different approach
= enqueue unique work
= in doWork:
- before showing notification
- check images that are not uploaded
- if images are to be uploaded, show a notification
- progress is updated based on % of images uploaded