pranavgupta1234 / hppoliceassistant Goto Github PK

This is arguably right way to present checkboxes. In the old app made in ionic checkbox experience was much better maybe bcos of cleaner UI, and also the fact that we can touch anywhere on the row (and not specifically at the little square) to toggle the checkbox. The way I use my hands to use mobile I think checkbox position should be on left side of label. This is not an urgent issue.

User does not need to add image from Gallery but from Camera.

Just two sample Challan IDs I observed till now:

CKINRPE435138769
CKINBNA818195501

What is the algorithm followed for these numbers. I believe C is for Challan, KIN for Disttict Kinnaur, RPE for Reckong Peo or BNA for Bhavanagar ...till here its perfect but 9 digit numerics after these alphabets is too long.

If I did not logout my last session then on relaunching the user should stay logged in.

Whether this is really useful can be discussed here.

Solved by specifying android:inputType="textPersonName" on I/O name

If user did log out last session then login screen should open next time app is opened. In this case details of police station, district, IO name should be prefilled (except for password) so as to enable user for quick login.

Login is independent of io name

When the image in stolen section is tapped to zoom.. the zoomed image is cut from the sides

Splash screen although looks good but it causes delay in using the app.

e.g. Challan form title is incorrect

Officer Name will be same name used in the login window (i.e. Pranav in the sample login) If the app can autopopulate it directly, it will be good.

In search section the search option starts sorting as we type...
while that in stolen section works only when we tap on search in our keyboard
and i think the better one is which is in search section that automatically starts sorting as we type

Solved

e.g. Instead of simply writing "Submit" the button can say "Save Data". (This can be discussed below)

After the Submit Button, you have provided three options, Edit, Online and Offline. Option of print (using Bluetooth Printer), have you been able to do it? That option will be a good option.

In the same print slip put space for Police Officer Signature and Violator Signature. Order for printing of all the details is already present in one of my comments in one issue raised by Gopal.

Since the user would not know that the Phone number field is a 10 digit field and he may start from +91 (10 digit number) and then face error so to warn him before hand. Name of the heading "Phone Number" has to be changed to "Phone Number (10 digit number)".

Similarly, For heading "License Number" it has to be changed to "License Number (no special characters)" and for heading "Vehicle Number" it has to be changed to "Vehicle Number (no special characters)* ". Asterisk is for pre-warning to the user that its a compulsory field.

Similarly, for heading "Name of Place" it has to be changed to "Name of Place * ". Again Asterisk is for pre-warning that its a compulsory field for the user.

we can arrange them in some priority order

Date and Time if could be autopopulated like was in the previous version, it will be good as it would avoid chances of fake challan. GPS coordinates were there in the previous version, you can retain it here too.

Please save date and time as a single value in firebase that is the number of milliseconds since the UNIX epoch. @pranavgupta1234 please do this asap

When I submit one challan with same details and next time again try to submit it again. It says Upload Done followed by Already Present! When I check for the challan in the search window, it comes to light that challan didnt get upload for the second time. Basically it should get uploaded in the database and officer can search for offences by the same owner/violator/phone no etc in the other window.

In the Offences checkbox field (like it was in the previous version of the app too) One last check box is required for Others in which one should be able to type the offence not covered in the checklist.

During Entry constables commit mistake in typing (e.g. while entering phone number 9882762624 they will enter 9882762624(space) or 9882762624% or 09816662225 or +91-9882762624. So to avoid such errors in Violator Number section put a background check that only 10 digit phone number can be added devoid of special characters/space, etc.

Scenario: if a same vehicle gets challaned at two different places by two different people and suppose one of the I/O uses slashes and hyphens and the other I/O doesn't. Now in our database, we have two challan entries of same vehicle but with different format. one may have HP/12/AB/2343, other one HP12AB2343. I have a feeling that this inconsistency can create a problem in future.
Therefore it is perhaps best not to allow ANY special character in vehicle number, license number.

e.g. after user loses focus from Vehicle Number field, app should check if it was correctly entered or not and if user did not enter (or correctly enter) the field an error message on the field (as is being displayed already) should be displayed. This is in contrast to validating after pressing Submit button

To save user's time, Naka name can be automatically populated to what user had entered last time.