3 ms·
I'm going to take a different angle: Don't build a GUI if you don't have the skills to build a GUI. You won't be able to compete on features in the long run, a
by 3pt14159 9y ago
I'm going to take a different angle:
Don't build a GUI if you don't have the skills to build a GUI. You won't be able to compete on features in the long run, and you certainly won't be able to compete on design in the short run. And certainly not without devoting 100% of your time towards it.
Instead realize that there are three primary types of interfaces that are in wide use today: GUI, API, and CLI.
If you're a backend dev the last two are much easier for you to build. So instead of building a GUI, build and API. Hire a designer to design you a basic 1 page marketing site. Keep it simple. Put up API docs on http://readme.io/ http://readme.io/ or something like that. Then iterate on features. Once you solve someones problem well enough find a second person. Iterate until finding leads is your primary problem, not closing them. At that point switch to marketing fulltime.
- 0xJRS 9y agoI think if you could build a mvp front end and get started then by the time you have to worry about competing on features you're already at a point where you'll have the resources available (skills and/or employees).
- jnbiche 9y ago> So instead of building a GUI, build and API This is a good idea. Indeed, if the software is useful enough, people will build free, open source GUIs and CLIs for your API. Just look at the open source mobile apps and CLIs popping up with DeepL translation system, for example.