The source of this would be useful to integrate such features in other apps (like editors). An API might do as well at least for online tools like blogs. As a standalone site it's too much hassle to integrate it into your daily workflow I think.
Making this an API that WordPress, Draft, Ghost, and other writing platforms could pull in would be awesome. Maybe you could add plugin support or something for people that want it integrated into their blog/cms?
You raise a good point: how should a "language linter" be integrated into the authoring workflow.
I write mostly in plain text and have developed a bunch of command line writing scripts to check readability, passive voice usage, and naming conventions, but I'm not sure how I could share this with my less tech-saavy friends.
Should the language tool be integrated into the editing interface or be an external service?
Assuming an external service, how should it be integrated with CMSes (wordpress/dokuwiki)? Should the source, normalized plain text, or HTML be sent to the language service for checking? Where do the corrections/edits happen?
As far as the business model is concerned, I'm not sure there is money to be made in this as a service to end users, but if this system is integrated as part of a complete workflow for edits/corrections some publishers and freelance editors might be willing to pay for this---not as the final check, but as a self-service "run this before you submit to me" requirement they give to authors to prune the low-hanging fruits.
