In general the UI for Ulysses is very thoroughly thought out, and somewhat idiosyncratic for that fact. Many people find it lacking or uncomfortable in one way or another, but I can tell you that every element of the UI has been considered and applied to fulfill the designers' very specific goal.
One of those UI values is that it's very semantically correct. There's no formatting at all, except auto-formatting that you define yourself, which will recognize plaintext tags. The way this shakes out is that I will write a sentence like this: The &&quick&& brown fox jumps over the lazy dog.
And then define a tag called 'emphasis', which is formed by a '&&' wrap, and displays itself in a certain way depending on whether it's being viewed in a window, fullscreen, printed, et cetera.
If you are a fan of working in plaintext and you are interested in more structured ways to write long-form text, I think it's a great program.
EDIT: changed example markup to something more exotic for HN's own parser
Preferably not a data silo; I push all my actual writing to Github with each revision, so a plaintext format that could come along for the ride and wouldn't require a special viewer would be nice.
EDIT: You might mean, "what's a composition interface?" In which case it's a text-editor component, with some added UI sugar like current line highlighting, word count, splitting, typewriting scrolling, full-screen mode, et cetera. You know, an interface for composing text.
So you could define markdown in it? I googled a bit, and only found people wishing you could, so maybe there's something I'm missing.
My main criticisms:
* updates come far too infrequently.
* little support for multiple versions of a document.