User Workflows

There are several ways into the program: let's flesh them out.

Customized UI

To a certain level, users should be provided with customizable and preset-customized ways into AUMI. Customizations include:

• removing some device support line external cameras
• removing classes of instruments like loops or relative motions
• removing some tracker support like distance or face
• removing more "advance features" like Timing and chords

and similarly:

• allowing SOME parts of some features, like just the "last" part of timing
• enabling experimental features like new trackers or rhythms
• making a customized preset list of instruments

Since people are rightly concerned about cookies and browser and backend databases, these should be keyed via GET query parameters like: https://aumi.app?simple=1

There's a whole question of being able to log in without it being an identity leak of some kind. I may moot that question by using third party services fro conferencing that makes it their responsibility to keep identities safe. Joining a session might need to be accomplished in an out-of-band method, like sending a temporary access code to the participants. This is done with the networked audio app "FarPlay".

main permissions

HTML Browsers need to set permission to use some advanced features.

Network AUMI users

• establish the level of detail for adaptive technology combinations
• • we'll need HTML5 permissions for
• • • cameras
• • • • which ones are made available
• • • • what is the order (default on top)
• • • • for each camera:
• • • • • fitting (fit, letter box, blur box)
• • • • • zoom
• • • • • orientation 0,90,180,270, 0F,90F,180F,270F (F == flipped)
• • • • • brightness, contrast, might be automatic
• • • • • clean plating?
• • • MIDI permission - depends on whether we do that
• • • networking with websockets? might not need it
• • • permissions for sharing setups and using shared setups
• • • • could be like Unix user, group, all permissions
• privacy and legal disclaimer consent
• come back using the last known setup or pop up a list of shared preset setups

Network AUMI Admins

• authentication
• protection from bots
• permissions for r/w access to the database
• user and group setups
• establishing a hierarchy of sessions and session admins
• permissions on cloud based setups
• permissions on aumi instruments