Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Goal: Separate out PCP, PMT or BOTH (PCP+PMT) designs for specific developer teams, WITH contextualisation


First use at PCP:

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)

First use at PCP: (Sophia at the museum)

> 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?

First use PMT (maybe Sam?)

return to PMT (new device setup?)

Return to PCP (pick a Sam)

with existing account
offline use?

First use DT

save to P**?
very simiilar scenario to first use PCP w/ no saving