Thank you! I've got some pretty cool ideas - at least they sound cool in my head :) - on what can come next. I'm insanely excited for a feature I'll probably put out later this week or next.
I and a friend have been doing something I think is a little better for a while. We just have the document in github, and use a jekyll task to render it, so you can edit it in your markdown compatible ide and sync to github, you can edit it online on github, you can add notes to specific line numbers in commits, you can submit pull requests, get notifications, etc., etc.
In fact, I was thinking about writing something a bit like this that used github as a backend, since it's working so well.
I'm a huge fan of IA Writer, there's a couple of areas where I think it could be improved though. Being online is one of them, the other being an option to show bold/italic/underline formatting (as opposed to just markdown syntax).
One difference that's immediately obvious using Draft is the home icon and mark draft button in the top right. Compared to IA writer it feels like unnecessary noise. It would be great if these faded out when you started typing and only came into view when you move the mouse.
I want to second this. It's already quite nice but I'd recommend being as extreme as possible with optimizing for focus. I don't need all the corner information, so let me have the option of turning it off or having it fade out.
Also, I don't know why the title defaults to all caps; some people may want to make decisions about the capitalization of their titles.
If you can figure out a way for people to try Draft without forcing them to register, do so. I wanted to play around with it, but I don't want to make yet another account. The more people who play with it, the more people who will sign up.
Thanks Scott. To be honest, I really debated that. I have a blog post or two on this topic specifically. I've gotten a lot of advice from smart people that goes both ways on this. I personally like a guest user experience and no sign up. But from a lot of a/b testing with previous products, I've seen requiring registers to have a great effect on being able to increase signups, but more importantly create valuable conversations. Namely to discuss problems and feedback, which helps me make something much more valuable for people.
I assume that by "increase signups," you mean that when people view the landing page, a higher percentage of them signup. But what would worry me is the stat that such testing does not capture: the number of people who did not share the site with others because it's not easy to play with. And that kind of sharing is advertising.
In other words, it's possible to have a lower signup percentage, but more total signups.
The wisdom I've heard is that you can either lose people on the "what is this -> signup" phase or the "signup -> pay" phase. Your leads are better qualified if you lose them on the former. You get better gauge of the potential market on the latter (guessing on this one).
Keep in mind that requiring users to sign up before trying the product contaminates user count as a meaningful metric, and devalues it as a marketing channel because it's filled with unqualified non-users.
I totally hear you that it sucks when you know people try your product but leave without signing up, and worse still you have no channel to ask them why. Users exploring a public demo have shown real interest in your solution to problems they have, and while they're exploring (especially if the demo is somewhat guided) there's a very natural opportunity to begin a conversation without requiring a signup. Ask for feedback (via survey, olark chat, quick submit comment form, your contact info...), offer to email product updates or tease future enhancements, show you twitter feed, etc. Moving registration downstream doesn't have to mean you can't learn about potential customers.
I can see your reasoning behing making people sign up, even if that will significantly retard your growth rate multiplier.
But there's NO reason to make people create a new account. Everyone hates making new accounts, and there are a zillion identity providers out there, from google to facebook to twitter to linkedin to github to yahoo (ad nauseum).
And even if it's too much work right now to configure your application to accept third party identities, you can still "sign-up" users by requesting an email address, letting them straight into the application, and then email them a URL with an embedded identity token that allows them to pick up where they left off.
My advice would be to give people something for signing up. For example, let them start playing without email, let the save, and then ask for their email address to send them a unique url to their new account. This has the added advantages that (1) more people will play with the app and hopefully talk about it! and (2) those that sign up are more qualified leads as they know what they're signing up for.
I've worked in two completely different companies where we tried some notion of using the product without signing up. Both times we just got more people with less overall engagement at the cost of complicating the backend infrastructure.
Not to say this will never work, but it's definitely not a panacea.
Came here to say this too. I hate making new accounts. I was really hoping I'd click try and be greeted by a blank word processor with a blinking cursor. Instead I got yet another login screen and I bailed (for now).
It seems to me Draft's key growth action is getting users to share a draft with a friend.
Design the user's first required action to relate to sharing; capture the author's email after they click Draft/Save, and their friend(s) emails when they want to share. The interface could use a little work to encourage sharing as well.
This product is designed to spread itself inherently, so play to that strength!
Just to add my twopenneth from running https://www.writelatex.com - allowing users create documents and start trying out the editor without signing up has been a big plus for us in terms of users, and is generally popular according to feedback.
And in the early stages, more exposure through more users is a good thing, helps spread the word.
For us it was the way we'd started out though, so easy to implement :-)
Come to think of it, I felt the same way. Left the registration page up in the background while I worked on other stuff. Eventually came back and made an account.
Login flow and initial writing experience all seemed excellent, and I'll be recommending this to some friends over GDocs for their next collaborative project.
The only niggle that immediately stood out to me was that the buttons on the "Import" modal are using the default Bootstrap styles instead of the flatter ones used throughout the rest of the interface. I doubt it would've stood out to me had everything else not seemed so carefully considered.
It doesn't currently support collaborative editing, if you have the doc open in multiple windows it's last save wins. I'd love to see this added a la google docs but I imagine it's a big step on from where they are now.
That's true. But the flow I use to write doesn't require any kind of real time collaborative writing.
I don't want someone writing on top of what I'm writing. I just want me there, and then you can work on your own copy of my work, and I'll choose what wins.
That being said, I definitely need some more real time experience here alerting you when someone is editing your doc and when it's ready.
I was one of the beta users and it's great to see this keep improving. I'm glad Nate upgraded the prices for editing. That's the feature that attracts me the most.
I agree. It does a good job of flagging misspellings, but it's lousy at offering suggestions. The weird part is that you can put the the same misspelling into google search and 99% of the time the "Showing results for..." is the correct spelling.
Google Search and Google Chrome are totally separate products within a massive company. (The same situation is why Gmail had terrible search for so long.)
I'm can't tell what the benefit of Draft is supposed to be, but for folks looking for a great tool for writing longer works, check out Scrivener. Bit of a learning curve, but once you get the hand of it you'll really appreciate the ability to work at a paragraph, chapter, or document level, and to pre-determine formatting for different outputs (p-book, e-book, etc.).
(I have no financial connection to the company - just wish I'd found it sooner.)
FWIW, I thought the features page[1] laid out Draft's value proposition fairly well, primarily around a collaborative and versioned writing environment that doesn't suck. I really like the idea of integration around other cloud tools, as it provides paths for Draft to work with my existing workflows instead of being Yet Another Cloud Island.
I'm not a heavy-duty writer, but Draft fixes some deficiencies in other tools well enough that I'll definitely try it for collaborative writing work.
As far as the Draft site, I'd like to see an easier route to the value prop on the features page from the homepage. Perhaps locating that info "almost below the fold" on the homepage, so that simple scrolling leads readers through a tour? I suspect (anyone have data?) that there's a lot of propsective users who drop off before they'll click on a "Features" link.
Thanks, I have some plans to experiment with the homepage for sure. I have a neat ab testing tool I made for a previous project that will get a workout. I'll open source that tool soon.
I used Scrivener for a book recently. The basic format was short chapters within sections (non-fiction). Scrivener did a great job as it let me easily rearrange things, easily track the state of chapters, etc. As for formatting though, once I got to the 80 percent or so point, I dumped the entire thing to a conventional word processor and finished it up that way. I don't use it for shorter pieces but I really liked it for pulling a book together.
I just pasted in a 4500 draft that I'm currently working on, and plunged right in. It's going great. I particularly like the side-by-side revision capabilities.
One problem: My current text is set to word-wrap at 80 characters. But Draft has word wrap at about 50 characters, resulting in ugly lines. How do I un-wrap my current text?
Yuck, sorry about that wrapping problem. I'd like to fix that. Could you send me that document (or something similar) that I could use to test with? I'm at nate@cityposh.com
I don't get it. It's just a page with markdown that lets you hire a pro for some editing help. I don't think the export feature is that exciting either, even though it's 'good', for example it lacks the option to export as pdf or any other popular file format that people might want the document in. When I tried to download my document to my computer I got a .txt-file... Now that's helpful.
The main benefit doesn't seem to be in the editing of Your Document, but in your collaboration with others and version control of the document. There are specific pain points of using Google Docs or git which this seems to deliberately address.
This looks really cool. I'd definitely be interested if I had the option of hosting my own instance. My line of work requires collaboration but borders matter in regards to where things are stored geographically.
It would be nice to see this built out like a service that desktop apps could tap into like Simplenote. I'd like to be able to use this with Byword for OS X. Dedicated desktop apps provide a nicer writing environment, but the ability to work in a versioned editing environment from any computer with a modern Web browser is a pretty big deal. I'd pay $1.99 a month for Draft if desktop apps could integrate with it or if Drafts could integrate with Dropbox.
Draft is integrated with Dropbox :) Through Filepicker.io you can import text/markdown from Dropbox, Evernote, etc. Any changes you make in Draft sync back to their location in those cloud service. The sync doesn't go back though from Dropbox to Draft, yet...
The idea of marking major drafts is genius. It's a happy medium between the show-you-every-change-you've-ever-made approach of Word and the latest-version-is-everything approach.
I would recommend integrating with publishing services, so I can edit my, er, drafts in Draft and then hit a single button and publish to WordPress, Tumblr, Medium, et al. once I'm happy with it.
Aww. Thank you. I'm incredibly flattered by this feedback.
I agree on figuring out something about publishing. I've got something really neat coming out this week or next. It's very simple, but it'll be one of the most useful things to my current writing workflow. Stay tuned...
Any larger text I write in ms-word I usually start in outline mode. This lets me easily set up an outline for the complete text, and reorder draft text until the structure of the text works.
For me any tool focused on drafting text should have an outline mode.
Dammit! I was joking on Twitter with a few people that this went unnoticed for so long in this discussion. :)
You know. I actually had written "someone's" in the original draft of that page. But I thought to myself "someone's at the door" and convinced myself "someones" must be the right word.
I think my wife even corrected this, and I didn't accept the change in Draft :) thinking I knew better. (Facepalm)
Did anyone have trouble running this in Firefox ? I'm on Firefox 20, Windows 8 x64 and the site is non-functional after logging in. I cannot create any new documents and clicking on any UI element does nothing.
It works fine with no issues in Google's Chrome Browser though.
I'll look into this. I've been making apps for so many years, and I'm always humbled by how much browser testing I have to do, and what is still broken after testing in like 8 browsers already. :)
I like the look of this, and the draft-marking is a great feature. I'd worry about using it in earnest, though, because it of its limited export options, which require the formatting to be done outside Draft. It's great to be able to collaborate on creating content, but a lot can go wrong in that final formatting, and Draft doesn't have a way to make that stage collaborative and version-controlled. Everything I write could be written in Draft, but none of it could be finished in Draft, and I see that as a problem.
116 comments
[ 4.7 ms ] story [ 190 ms ] threadhttp://imgur.com/Imb7EJE
Should be a relatively easy fix with some background-fu applied to the footer.
In fact, I was thinking about writing something a bit like this that used github as a backend, since it's working so well.
One difference that's immediately obvious using Draft is the home icon and mark draft button in the top right. Compared to IA writer it feels like unnecessary noise. It would be great if these faded out when you started typing and only came into view when you move the mouse.
Also, I don't know why the title defaults to all caps; some people may want to make decisions about the capitalization of their titles.
Great work though!
You are right, people really do like to make decisions about this stuff. I'll see what I can do.
But do I like Future Bold in caps. Just love it :) The underdog font as Aaron Draplin would say.
In other words, it's possible to have a lower signup percentage, but more total signups.
I totally hear you that it sucks when you know people try your product but leave without signing up, and worse still you have no channel to ask them why. Users exploring a public demo have shown real interest in your solution to problems they have, and while they're exploring (especially if the demo is somewhat guided) there's a very natural opportunity to begin a conversation without requiring a signup. Ask for feedback (via survey, olark chat, quick submit comment form, your contact info...), offer to email product updates or tease future enhancements, show you twitter feed, etc. Moving registration downstream doesn't have to mean you can't learn about potential customers.
But there's NO reason to make people create a new account. Everyone hates making new accounts, and there are a zillion identity providers out there, from google to facebook to twitter to linkedin to github to yahoo (ad nauseum).
And even if it's too much work right now to configure your application to accept third party identities, you can still "sign-up" users by requesting an email address, letting them straight into the application, and then email them a URL with an embedded identity token that allows them to pick up where they left off.
Not to say this will never work, but it's definitely not a panacea.
just started typing as soon as it opened which felt like a good change from adjusting fonts
We all have Google accounts. Just use those, devs. You even get two-factor for free.
I rarely sign in with Google for any app.
Design the user's first required action to relate to sharing; capture the author's email after they click Draft/Save, and their friend(s) emails when they want to share. The interface could use a little work to encourage sharing as well.
This product is designed to spread itself inherently, so play to that strength!
And in the early stages, more exposure through more users is a good thing, helps spread the word.
For us it was the way we'd started out though, so easy to implement :-)
Others might not be so patient!
The only niggle that immediately stood out to me was that the buttons on the "Import" modal are using the default Bootstrap styles instead of the flatter ones used throughout the rest of the interface. I doubt it would've stood out to me had everything else not seemed so carefully considered.
I don't want someone writing on top of what I'm writing. I just want me there, and then you can work on your own copy of my work, and I'll choose what wins.
That being said, I definitely need some more real time experience here alerting you when someone is editing your doc and when it's ready.
I'll get those styled soon.
Thank you very much for this feedback.
"whatever password" has to have at least six characters - maybe you might want to clarify this
(I have no financial connection to the company - just wish I'd found it sooner.)
I'm not a heavy-duty writer, but Draft fixes some deficiencies in other tools well enough that I'll definitely try it for collaborative writing work.
As far as the Draft site, I'd like to see an easier route to the value prop on the features page from the homepage. Perhaps locating that info "almost below the fold" on the homepage, so that simple scrolling leads readers through a tour? I suspect (anyone have data?) that there's a lot of propsective users who drop off before they'll click on a "Features" link.
[1] https://draftin.com/features
One problem: My current text is set to word-wrap at 80 characters. But Draft has word wrap at about 50 characters, resulting in ugly lines. How do I un-wrap my current text?
I would recommend integrating with publishing services, so I can edit my, er, drafts in Draft and then hit a single button and publish to WordPress, Tumblr, Medium, et al. once I'm happy with it.
I agree on figuring out something about publishing. I've got something really neat coming out this week or next. It's very simple, but it'll be one of the most useful things to my current writing workflow. Stay tuned...
[1]: http://www.iawriter.com/
[2]: http://www.ulyssesapp.com/
>You don't need writing software; you need someones feedback on your writing.
It should be "someone's" or, ideally "you need feedback on your writing." I don't usually do this, but in the spirit of the page...
You know. I actually had written "someone's" in the original draft of that page. But I thought to myself "someone's at the door" and convinced myself "someones" must be the right word.
I think my wife even corrected this, and I didn't accept the change in Draft :) thinking I knew better. (Facepalm)
It works fine with no issues in Google's Chrome Browser though.