Here is how it goes: - you slap together a low effort UI in order to test your code. - You use this UI so much during development that it becomes "intuitive"

Here is how it goes: - you slap together a low effort UI in order to test your code. - You use this UI so much during development that it becomes "intuitive" for you. - Early adopters are interested in functionality, so they can overlook a poor UI for a while. - They use this poor UI so much that it becomes "intuitive" for them. - Early adopters even help newcomers to overcome the poor UI. - Meanwhile you develop more features and postpone the "less valuable" UI improvement. - At some point there is so much functionality hooked to the UI that it would be a drag to change it. Also as it was quick-and-dirty stuff it would also be very difficult for others to redo the UI. - You find a way out: pretend that it is vital to extract the library hidden in your program, so that "anyone will be able to put the UI they want on top of it so leave me alone". - This further postpone the new UI, because potential UI makers have to wait until the library is done, and then users have to wait until the UI designer and implementer does their thing. - It takes too long because portability issues and API design is not so easy, so you lose your UI designers one by one. So you have to make a low-effort UI to test and demo your library.