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

P7

Key findings

  • There are connectivity problem with mobile, in particular that it’s sporadic. The platform dictates when and where any networking happens.

  • There are restriction use cases and generally they are 30 seconds and then you put the phone back in your pocket, therefore it’s less beneficial to have a full node

  • Early adopters as users, such as with Textile Photos, are ones frustrated or paranoid about Google looking for alternatives and they are willing to put up with a lot

  • Data sync issues constant sharing of photos different states felt unsolvable - data discovery issues

  • Look for data on networking and it just times out

  • Don’t remember specific level of feedback

  • Users don’t want to know they’re running a node, it should be invisible

  • The end goal should be the user having siloed data not application silos. It should be flexible and the user would have choices when you need to authenticate with your ID and choose the provider like OAuth. Thus the user should depend on the provider for the user experience which could be long password to email to anything

PreviousP3NextP14

Last updated 5 years ago

Was this helpful?