Hi everyone - we have some updates to share!
We had a call with the HOT team this week, and everyone is aligned on the file picker and device storage. We've also iterated and refined the user experience to hopefully meet everyone's needs. Here is a mockup to give you an idea of the direction and what we are going to start building 
Key design considerations
-
Information hierarchy: clear titles, descriptions, and CTAs so users understand what they are looking at and where to go if they need more information.
-
Add/delete MBtiles layers: We included the ability to delete because the layers could be large. We are still unsure if delete is critical for the first iteration.
-
Keeping the path: Without an option to delete there would be more manual management. We decided to keep the path in the UI because titles could be the same or similar, and the path could have helpful information (e.g. determining if the layer is shared between projects or only at the project level). It also means users could use adb to connect from a computer if they want. By hiding the paths, it makes it easier to scan if you have multiple layers to choose from.
-
Navigate via map or settings: the same functionality would be in both spots, although we assume discoverability will be higher from the map question.
Feedback
-
Terminology: in the mockup we use the term "reference layer", but we've also been considering "MBtile layer" or "offline layer" as alternative options. What do you think would be the most clear for data collectors?
-
We are curious to know what you think. Let us know in the thread, or give us a thumbs up if you like the direction.