search

element-hq / element-ios

A glossy Matrix collaboration client for iOS
https://element.io
GNU Affero General Public License v3.0
1.73k stars 499 forks source link

Add Riot to the share content menu on iOS #514

Closed giomfo closed 7 years ago

manuroe commented 8 years ago

The share content menu is an extension of the app with its own design. What UI do we want to display? A list of rooms? A list of matrix users? A list of contacts?

giomfo commented 8 years ago

We need a design for an app extension launched when the user decides to share a content through ios vector.(see https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/ for app extension).

Which kinds of picker shall we display to share a file/an image...?

antikewl commented 8 years ago

I think we have a couple of options here:

  1. Follow Messenger's example by allowing the user to search anything from a single form: messenger_step1 messenger_step2
  2. Similar to the above, but split out groups from people with tabs: facebook_picker
AmandineLP commented 8 years ago

/me votes option 2 with "rooms" and " People".

If doable (@giomfo please confirm) "Room" first item will be a new room "People" first item could be a field where we can enter an email @ or matrix id to start a chat with a new person.

giomfo commented 8 years ago

option 2 wfm too

masvil commented 7 years ago

I hope this feature will have higher priority in the next future because of its importance for a mass adoption. At this time iOS version is the only one still missing it.

I think a "pulling" technique (starting from a "+" button linking to the Document Provider list same like Whatsapp) should be better than a "pushing" technique ("Open in" from an external app like described in above comments) because more user-friendly and more adhering to modern standards.

jooize commented 7 years ago

I hope this feature will have higher priority in the next future because of its importance for a mass adoption.

I think this is important and underestimated. It's neglected in Signal as well. When I want to send a picture, the extra steps of going all the way off into the app and …

Pulling attachment in app

  1. Take or realise you want to send a picture (or other asset) currently on screen.
  2. Switch to app. (usually multiple steps)
  3. Go into conversation (which may include leaving a conversation you were in).
  4. Press button to add attachment.
  5. Select where from you want to select the attachment (Camera, Photo Library, any Document Picker).
  6. Find the picture.
  7. Attach. Don't immediately send as Signal does. I find that insane. One mistap and you've sent a sensitive picture to the wrong recipient(s).
  8. Send.

Pushing attachment from anywhere

  1. Take or realise you want to send a picture (or other asset) currently on screen.
  2. Press Share button.
  3. Choose app.
  4. Select recipient(s). May be one or multiple steps depending on implementation and target(s).
  5. Send. It could make sense to send immediately when selecting a recipient if potential for mistakes are low by design.

Both of these should be implemented of course.

masvil commented 7 years ago

Both of these should be implemented of course.

I really agree, same like popular iOS apps.