![]() And if it ain’t broke – why fix it?īut, when I talked to more developers it was interesting to see their thought process wasn’t quite as simple as “I like that demo!” Stage 3 What makes you choose one WYSIWYG editor over another?įrom my experience in using TinyMCE when I was actively developing, I knew that many decisions were often a case of being familiar enough with a tool that you picked it off the shelf again and again, because you trust it. How do you actually decide which one is right for you? So to continue, let’s assume that all potential rich text editors have easily accessible demos to play with. Afterall, are you really going to pick a solution for your app if you haven’t had a chance to use and play with it yourself beforehand? Providing a demo for developers to explore is not only helpful, it’s essential. It was like all the stars had aligned… and everything suddenly made complete sense to me. I played with the demo, looked at how easy it was to get started and then put it in my app.” He replied: “I followed the process that I follow whenever I'm looking for something in my app, or for a component … I just, like, Googled it, and then I went on the website. ![]() I started off by asking: “So, what made you choose that editor?” ![]() And given he’d just selected an open source editor for his project, I wanted to know why he chose the one he did. Demos are the first place developers go to help them make a decision on whether to try or pass on new software.Īfter approaching a friend – a full stack developer currently working on large scale projects – I had lots of questions about the search process. ![]() Speaking with a developer was crucial in the discovery of finding out what editors were best.īecause it revealed a major insight that may seem obvious to some readers, but can be often overlooked – the importance of demos. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |