Earlier quoted context omitted.
This will be a tough sell. Org-mode is a fairly fast moving target, due to how easy it is to extend anything in emacs. For lots, you will actually be battling against all of the other extensions in emacs. (For me, as an example, you will have to replace flyspell, beacon, tramp, ace-jump, ido, and ggtags.) All of this is doable, of course. But it will be a tough sell. That said, I'd say go for it. Worst case, nobody u…
Yeah, it would be fairly difficult to build, which is why getting feedback would be useful, but there's a catch 22; people who already know what Org is are fairly comfortable using Emacs and I don't know how to find out if people not that found of Emacs itself would still find Org useful, or if combining apps like Ulysses and Omni Outliner is good enough for them - the worst part is that because they don't use Emacs,…
I think that could absolutely kill it.
Imagine writing extensions in js or lua or whatever, and having those extensions have clear DOM-like access to the outline, have full access to their stdlib, have access to built in services like notifications, etc.
Imagine being able to programmatically access and manipulate the outline from wherever: webhook to add an outline node from IFTTT, twilio access your notes? etc. Yes you _could_ do that with Emacs, but IMHO it would take an incredible amount of work to not suck, partly because all the various pieces necessary feel like hacks on top of hacks.
Sort of how Atom and VSCode provide _much_ better interfaces (both code and UI) to your source code, and are starting to make honest inroads against the established players (like Emacs and Vim).