The enrolled screen is actually the 1st screen in the app.
so clicking Back (after enrolling) - will take you back to the enrolled screen.
Just a little glitch on my part - I thought I trapped it, I guess not , shouldn't cause any issues, just don't click back - but terminating the app (swipe up) will always bring you back to the ready screen (providing you enrolled)
Yup - I thought I trapped it - I'll fix it on the next update.
but providing you enrolled - killing the app (swipe up) should take you back to the ready screen after launching it again
Looks like you have enrolled your phone. So the next step is to try creating a flow.
Maybe use one of the "examples" so you can have a go at scanning a barcode.
Had a cool use - documenting large purchases, where they can then be reported against (given a user input screen can be presented to provide the purchase information)
If you want to know where this all come from.
We now scan asset tags in work, and can bring up history for the scanned asset (or add the new asset info, if not found)
It was never possible - until I made it possible
We have around 400-500 assets across the country
I wrote a Telegram + Node-RED bot for two of my grandsons who have recently started at university. The idea was to manage their fridge/freezer/pantry - which the bot did really well.
I might have a go at adjusting the front-end to make use of BARRED.
In your situation you'll need a database to track details of your spices.
The reason I used Telegram as the front-end was so my grandsons could access the dB when they are "out-and-about". In your situation you might be happy just checking "things" from within your home, so you could use a Node-RED flow "paired" with BARRED.
So being serious... the Telegram 'FridgeBot Receiver' would need to be replaced with an 'Incoming Action' node and likewise 'FridgeBot Sender' replaced with 'Send Item' node.
If I get some spare time in the next few days I'll have a go at revamping the flow.
Really probably not worth it unless you want to practice your MySQL-fu. Unless you are running an exotic spice warehouse, simply using a retained context variable should be more than sufficient.