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
  • What we found out in research
  • Design considerations
  • Who is the user and what are their needs
  • Putting it into practice
  • Open share menu
  • Select and share through App X
  • Confirmation to user showing CID link and button to open App X

Was this helpful?

  1. Design
  2. Scenarios

The user shares a file through another app

PreviousThe user onboards confidently with minimal technical knowledgeNextLarge file sent to user

Last updated 4 years ago

Was this helpful?

What users do not need is another app or service to do things they are already doing on their smartphones. Discovering and installing a new app is already a barrier to entry. A bigger barrier is managing another application to message or transfer data. This is especially the case when the user usually does it another way.

What we found out in research

  • are often hesitant to use new apps to do the things that are already handled by other other apps

  • are increasingly interested in not using cloud services to share files

Design considerations

  • Try to use the existing mobile OS and its conventions as much as possible

  • If your app has contacts stored already, utilise these for sharing as much as possible

  • Prioritise frequent contacts

  • Show a confirmation with CID, link or hash of the file

Who is the user and what are their needs

Student in early 20's who wants to send files directly between smartphones not necessarily on the same operating system without having to upload it somewhere

Putting it into practice

Open a photo in gallery or other file browser app on their smartphone

One very common user pattern is to share a file from the native application. This is especially the case with photos which are easier to view in photo gallery apps.

Open share menu

Major mobile operating systems such as iOS and Android have contextual share menus which work across the OS. App X would also be available for instance in this bottom sheet menu. The user taps this button to share with App X.

Design consideration

Try to use the existing mobile OS and its conventions as much as possible

Select and share through App X

A modal opens in the photo gallery app which shows the different share options for App X.

The user taps Email and enters in an email of a friend and then taps Add to network and send link.

Design consideration

If your app has contacts stored already, utilise these for sharing as much as possible and prioritise frequent contacts

Confirmation to user showing CID link and button to open App X

The CID of the image that has been added to the IPFS network is emailed to the entered email address and the user is shown a confirmation with the hash and a link to open the image in App X.

Design consideration

Show a confirmation with CID, link or hash of the file

Users
Early adopters