If keepass2android's functionality was extended, one should be able to store and display UPC codes for use at stores and organizations that use UPC codes for loyalty and member identification (grocery, drug, coffee stores, gyms, etc). Often this functionality is handled by separate mobile applications. Occasionally an organization needs a UPC to scan and a PIN, which gives a clumsy user experience and app switching experience. Could keepass2android support loyalty cards in the future?
One could store images of these UPC codes, however the .kdbx size can swell to megabytes, and not ideal for a mobile phone using cloud data storage.
Possibly this could be accomplished with two Additional Strings that a user could enter, with an example of:
[kpa2_UPC_Type]=QR
[kpa2_UPC_Value]=2YU8754565
UPC_Type would be a value of one of the dozen or so of different UPC formats.
UPC_Value would be the string passed to the library along with the UPC type that would return the UPC code
A picklist of the supported UPC Types may be more user friendly.
Most users might have problems determining what the data is on their card with a UPC such as to enter into keepass2android. They may need to scan it with another app, and copy that value into a future keepass2android version.
If keepass2android's functionality was extended, one should be able to store and display UPC codes for use at stores and organizations that use UPC codes for loyalty and member identification (grocery, drug, coffee stores, gyms, etc). Often this functionality is handled by separate mobile applications. Occasionally an organization needs a UPC to scan and a PIN, which gives a clumsy user experience and app switching experience. Could keepass2android support loyalty cards in the future?
One could store images of these UPC codes, however the .kdbx size can swell to megabytes, and not ideal for a mobile phone using cloud data storage.
Possibly this could be accomplished with two Additional Strings that a user could enter, with an example of:
[kpa2_UPC_Type]=QR [kpa2_UPC_Value]=2YU8754565
UPC_Type would be a value of one of the dozen or so of different UPC formats. UPC_Value would be the string passed to the library along with the UPC type that would return the UPC code
A picklist of the supported UPC Types may be more user friendly.
Most users might have problems determining what the data is on their card with a UPC such as to enter into keepass2android. They may need to scan it with another app, and copy that value into a future keepass2android version.