I agree. I think the mobile apps solutions need to also include an easier initial setup and login workflow. End result is where the site's server information and a user's account is automatically added to their mobile device. Also, it may be a good idea that the mobile app be flexible enough to allow for *multiple* servers. Some ideas:
- a first time *site/server setup* QR code could be displayed at or near all print devices
- Pharos could provide an opt-in "directory" service for Pharos site admins that allows users to search and find by institution name/acronym. Optionally it could be protected with maybe a keyword code.
- Autoconfigure by geolocation (allowing for multiple locations) via point+radius or polygon boundaries
- Possibly restricted via device IP ranges like 10.5.1.0/24,10.5.2.0/24
- User login integration with 3rd party providers like Google/Facebook/Twitter
- User login via SSO with one-time code/PIN like "link your TV"... "print.mysite.edu/login" or "print.mysite.edu/activate/mycodehere"
- For print centers/release stations, it would be nice if they could support maybe these technologies (browser technology is very advanced nowadays with better hardware integration):
- prox/NFC against the user's mobile device
- "webcams" to allow for logins using QR codes that can be displayed from within the app with:
- permanent user-based QR codes
- one-time or temporary (like one hour/day) QR codes
- with optional password or PIN entry at the stations.