IPFS Mobile Guidelines
  • Introduction
  • Context
    • Considerations for Mobile
    • Methodology
  • Application Survey
    • Mobile Browsers
      • Android Chrome
      • iOS Safari
    • Mobile Sharing Interaction
      • Android sharing
      • iOS sharing
    • Application Survey
      • ManyVerse
      • Sharedrop.io
      • Status
      • FrostWire
      • uTorrent Mobile
      • Haven
      • Fairdrop
    • Features Survey
    • Interaction Survey
    • Findings
  • User Research
    • Assumptions
    • Interviews
      • Experts
        • P2
        • P3
        • P7
        • P14
        • P15
      • Early Adopters
        • P1
        • P4
        • P5
        • P6
        • P8
        • P9
        • P10
        • P11
        • P12
        • P13
      • Potential Users
        • P16
        • P17
        • P18
        • P19
        • P20
        • P21
    • Findings
  • Design
    • Design Strategy
    • Design Workshop
    • Principles
      • Respect the device
      • Explain, don't overwhelm
      • Make privacy work for the user
      • Give control over data
      • Be seamless
    • Scenarios
      • The user onboards confidently with minimal technical knowledge
      • The user shares a file through another app
      • Large file sent to user
      • User plays a shared media file without wifi or mobile network
      • A user manages their chat identity
    • Findings
    • Credits
Powered by GitBook
On this page

Was this helpful?

  1. User Research
  2. Interviews
  3. Experts

P3

Key findings

  • Your ID is the sum of all the groups and all your online personas

  • Your ID should follow you around but you could choose what parts go where of your ID

  • People need level uptime for P2P like the current web and won’t compromise but users want privacy and agency now

  • P2P skews towards the global and the young but they expect native apps on mobile

  • PWAs break the user experience - don’t know how they persist on the home screen and if the data will get cleared

  • P2P requires a lot of user education

  • People are aware of this thing that is “the cloud” and know their data is in it somehow, but often not where it actually is, for instance with Uber rather than actually on AWS - they haven’t thought why it’s portable and what enables that

  • Things are moving back towards offline-first rather than cloud-first from the past eight years of depending on persistent server connections

  • We might see something even more radical happen which is moving towards mesh applications like FireChat - this is where the traditional web seems to be moving

  • Its not known what the UX costs for implementing JS in IPFS in terms of data usage and battery, etc. because it’s not been battle tested and developers won’t move on it until it is

PreviousP2NextP7

Last updated 5 years ago

Was this helpful?