and no.Īs it turns out, there are certain suggestions that people tend to always accept, and others that are more likely to require further consideration, depending on the writer’s specific need. Would this solution solve the problem our Premium users were facing? Yes. As we started asking ourselves what the minimum viable product (MVP) solution might look like, we could see that the simplest approach would be to just bundle all of Grammarly’s suggestions under one big Accept button. The problem was clear: Grammarly Premium users were spending too much time making clicks to accept high numbers of suggestions one by one. Though this feature presents a special case in which disparate pieces fell into place, in many ways this is also characteristic of our process at Grammarly-it’s an apt illustration of how we typically go from idea to launch and all the different teams that contribute along the way. From the natural language processing (NLP) model to the front-end and backend, this feature was essentially bootstrapped from various side projects that ultimately fit together in a cohesive way. We went through several iterations of the design, and had to carefully consider trade-offs to arrive at a feature that balances convenience and control in the right ways.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |