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
  • Respect the device
  • Explain, don't overwhelm
  • Make privacy work for the user
  • Give control over data
  • Be seamless

Was this helpful?

  1. Design

Principles

PreviousDesign WorkshopNextRespect the device

Last updated 4 years ago

Was this helpful?

The Principles provide an overarching rationale to the design of mobile apps and services that use IPFS. These principles cover the broad gamut of issues designers and developers might encounter. These are suggestions for designers and developers when building their apps and services.

Each starts with analysis taken from the . This analysis serves as a basis for deeper considerations for designers and developers. Each principle in turn includes Do’s and Don’ts on how to make it happen and an illustration of what it could look like.

Respect the device

Apps and services for mobile aren't reformatted desktop apps. They need to take into account a host of different issues, from battery life to signal.

Explain, don't overwhelm

Stategically highlight the unique and key benefits like privacy and speed that other apps not on IPFS don't have. Avoid long, technical explanations in interfaces.

Make privacy work for the user

There is no shortage of concern about privacy and security for all levels of users. What users want is assurance that they have some level of privacy or security so their data and files are safe.

Give control over data

Mobile apps and services should help manage files. They can do this by respecting the needs users may have with availability, discoverability and persistence.

Be seamless

The user shouldn't necessarily know how they're connected, whether through wifi, bluetooth or otherwise. They should just feel confident that data is getting sent and received, not how.

research
Read more
Read more
Read more
Read more
Read more