Goal: Separate out PCP, PMT or BOTH (PCP+PMT) designs for specific developer teams, WITH contextualisation
not saving (device only permits PCP functionality) (x at the museum)
slim options within the PCP based on available features for content
content matters
the implementer decides what the end-user sees
there's a notion of time here (museum wants to keep the interaction quick)
> Download wireframes
saving settings
alternative saving features (cloud + ticket)
save to cloud from kiosk with woman
use ticket to go from interactive to interactive
question about presets vs. prefs available to user?
need alpha-numeric input options to create account?
return to PMT (new device setup?)
with existing account
offline use?
save to P**?
very simiilar scenario to first use PCP w/ no saving