I have 3 types of objects for a delivery scanning app. 2 of these are types of containers, and the 3rd type are packages that need moved between containers.
There isn't much of an order to how these things should be scanned, that's largely on the user. But the general UI idea is, if you scan items of type A, then the A screen/view shows, if you scan B, it swaps to the B screen, and the same for C. These screens should be jumped between rapidly, as the user scans the different types. How should I persist data between these pages/views?
I have thought about ViewModels, or just 1 shared ViewModel, I've thought about the Application.Current.Properties, and I've thought about SQLite. Which of these would be the best way to store this data? To give an example of what should appear on screen, a list of opened containers could be on one screen, and a list of packages to physically move could be on the 2nd screen. As a user opens more containers with scanning, this list should grow, and as a user picks up and drops packages (using scanning) this list should also grow/shrink on screen, in real time.
I am also considering an invisible tab bar to handle the navigation of this quick switching, i.e. 3 tabbed pages that you don't see the bar for.
I hope that makes sense. Has anyone worked on something like this before?