wordpress-mobile / wordpress-mobile/WordPress-iOS
Suggestions for the app sharing extension
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3.9k
- Forks
- 1.2k
- Avg merge
- 23h 51m
- Merged PRs (30d)
- 58
Description
Hello, I'm one of the developers of Bear, a note-taking app for iOS and Mac. Some of our users expressed the intention to start writing a post on Bear and at some point migrate to Wordpress.
Since we are very pro apps integrations, I have spent some time playing with the Wordpress sharing extension as it seems to way to go to accomplish this goal but I found some limitations.
I thought about proposing some improvements that, in my opinion, can be beneficial for any app developer who wants a deeper Wordpress integration.
Expected behavior
These are my propositions for the sharing extension
- I wish the app sharing extension will allow passing the title, tags, and body as a separate "fields". I Think JSON or an NSDictionary can be a way to achieve this.
- Allows passing an attributed or markdown string as the body to preserve the styles used in the source editor
- The text passed as body is not shown as quoted text by default
- A way to pass attachments along with the body and their position inside the original text is preserved inside the preview. NSAttributedString may be useful for this purpose.
Actual behavior
The string passed to sharing extension is shown as a quoted text in the post preview.
Tested on iPhone XR, iOS 12.1.3, WPiOS 11.6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests, so first locate the WordPress iOS sharing extension and inspect how it handles the tested sharing flow. Compare its behavior with the requested title, tags, body, formatting, quoting, and attachment-preservation capabilities. Done would require an agreed scope and implementation of the selected sharing improvements, validated on the stated iOS and WPiOS versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100