vickychijwani/quill

Create new posts by sharing text/photos to the app

Opened this issue · 3 comments

vickychijwani commented

A user on Google Play requested the ability to share content from Google News to Quill, thus creating a new post. I can imagine other users might want to write in a different app (since Quill does not try to provide the absolute best Markdown editing experience on mobile) like iA Writer or Evernote, and only use Quill to upload images and actually publish to the blog.

Another related use-case could be quickly sharing photos on their blog from a Gallery/Photos app. That might be trickier to handle, because the image needs to be uploaded first.

RaringCoder commented

One of the reasons I use Quill is to get stuff off my phone to the blog quickly. Ideally I'd like the app to be a complete blog editing experience, but for the short term being able to quickly create drafts with just enough content to be useful when hopping onto a desktop to do full editing would be useful.

I'm a developer, but unfortunately not an android dev. I can take a look and try to start amending it, but I can't promise anything.

vickychijwani commented

One of the reasons I use Quill is to get stuff off my phone to the blog quickly. Ideally I'd like the app to be a complete blog editing experience, but for the short term being able to quickly create drafts with just enough content to be useful when hopping onto a desktop to do full editing would be useful.

Thanks for the feedback, that's actually useful context for me - it helps me design the app better. I've heard from another user who uses it in a similar way.

I'm a developer, but unfortunately not an android dev. I can take a look and try to start amending it, but I can't promise anything.

Honestly, the code is probably hard to get into at this point, especially if you're new to Android (and Android by itself has a steeper learning curve than desktop/web platforms I believe). Also, I'm planning to do a big rewrite in Quill v2 over the next few months, for several reasons:

  • Ghost is finally reaching v1.0, with lots of breaking changes in the API and behaviour changes in Ghost itself
  • The code is not testable at this point (in the context of unit/integration testing)
  • There are some deep-rooted issues arising out of the current architecture, and a rewrite would take them into account from the beginning (e.g., right now you can't undo/redo changes in the editor, and can't sync in the background)

I'm open to discussing this further though.

RaringCoder commented

Fair shout on the dev experience. More test coverage and a sandbox environment would really boost involvement. I'll hold fire for now then and just provide feedback ☺