-
Content Count
5,834 -
Joined
-
Last visited
-
Days Won
1
Single Status Update
-
Man, just a word to any programmers or software developers around here, from one of the kajillions of people who use your stuff:
If you make a purported video recording program and I can't intuitively tell how to just get it to record what's on the screen without having to dig around on your forum, you're doing it wrong.
Interface is not a secondary concern. Do not develop it as an afterthought, please. Don't look at it yourself as the programmer and think "well, that's good enough; seems simple to me." You developed it and wrote those controls. Make the interface for somebody who is sitting down to it the first time. Use familiar controls so that they can figure it out quickly without help.
That is all.
- Show previous comments 3 more
-
>writing in visual studio
>where the fuck is the compiler?
>looking through menus, options, found nothing
>had to google it
Even the fucking turbo pascal had in-built, easily accesible compiler ffs.
-
FlorbFnarb and Tarski reacted to this
-
Proper software has designers responsible for UX so devs know what to implement
-
FlorbFnarb reacted to this
-
Yeah, I remember good ol' Turbo Pascal. Good times.
This is probably heresy, but I can see the sense in starting with an interface first. It's a good way to know what you want to include, like you said. Might be a bit prone to feature creep, but a tacked on and badly designed interface will kill software commercially.