My org does a lot of construction supervision work, and we take a lot of photos. These photos are useless without context. Pre-appsheet, it was a logistical nightmare to get field personnel to upload and add context to photos stored on their phones. One solution was to use a third-party application (e.g. Open Camera on Android) to add text overlays to our images. Conveniently, if you set this as your default camera, AppSheet will use it and images will be stamped. If I can do this without having to rely on a third party app, then that makes user onboarding / training easier for me and makes workflows more consistent.
Note that images stored in appsheet will have context when viewed through the app (ref tables, date, latlong coordinates, descriptions, etc). However, these images are often shared outside of the context of the app. Having some metadata overlayed on the image is very useful.
Problem: a hurdle I often encounter with AppSheet is that it only allows a table to be
'ispartof' one other table. This means, for every unique inspection form one may have, you must have its own photos table. This isn’t desireable, particularly in an application with `10+ unique forms. Also, I want users to be able to view all photos in a single table rather than segmented based upon their unique parent tables… hopefully that makes sense
Solution: continue to add a unique photos table for every unique table, but set it to ‘filter out all existing rows’:
Add an OnSave action which takes only the image path, table identifier, and row REF and places it in a new, universal photos table.
Where this API comes in handy: I can set up my photos table similar to how you’ve shown in your demo video above. I don’t need to worry about all of the excess metadata being saved (text placement, color, etc) as it is effectively discarded on save. The edited image will be passed to my new table.