# On Android my Discourse is not always an option for 'sharing'

**URL:** https://meta.discourse.org/t/on-android-my-discourse-is-not-always-an-option-for-sharing/112176
**Category:** Feature
**Tags:** pwa
**Created:** [20 maart 2019 om 19:28 UTC](https://meta.discourse.org/t/on-android-my-discourse-is-not-always-an-option-for-sharing/112176 "2019-03-20T19:28:46Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [18 juni 2026 om 19:49 UTC](https://meta.discourse.org/t/on-android-my-discourse-is-not-always-an-option-for-sharing/112176/8 "2026-06-18T19:49:35Z")

</div>

Thanks for reminding me of this @southpaw!

> [@southpaw](#):
>
> So perhaps Discourse could offer a menu the same way, with options like:
> 
> - Create a new topic
> - Reply to an existing topic
> - Create a new PM
> - Reply to an existing PM

How this looks?

[![](https://global.discourse-cdn.com/meta/original/4X/3/0/2/302272efae920eab8df864944807ac960ff94d4c.jpeg "Testing Discourse Web Share Target v2") ](https://www.youtube.com/watch?v=LOTUBnd9uwA)

PR at

> <https://github.com/discourse/discourse/pull/41030>
>
> Previously, Discourse only registered as a Level 1 Web Share Target — a \`GET\` te…xt-only handler that could not receive images or other files from the OS share sheet.
> 
> This change registers a modern \`POST\`/\`multipart/form-data\` share target. The service worker intercepts the incoming share, stashes the shared title, text, url, and files in the Cache API, and redirects to a \`share-target\` route that opens a modal asking whether to start a new topic, a new message, or save the content to add to the next reply. Topics and messages open the composer pre-filled with the shared text and uploaded files; the reply option buffers the content and injects it into the next reply composer that opens.
> 
> \### Notes
> \- The file \`accept\` list covers images, video, audio, PDFs, and common document types; the server still enforces \`authorized\_extensions\`.
> \- Adds a \`composer:uploader-ready\` app event so shared files are only handed to the uploader once it is bound, avoiding a race on cold composer open.
> \- Only Android Chromium-based browsers currently implement file-capable share targets; iOS has no Web Share Target support.

---

_[View the full topic](https://meta.discourse.org/t/on-android-my-discourse-is-not-always-an-option-for-sharing/112176)._