Ask HN: Does anyone WANT to build client software anymore?
We've been hiring for RescueTime (a funded YC company) for about a month now. We found our first hire right away (a rails guy) - a classic YC-style hacker-- passionate, crazy-smart, seeking a small team with a clean slate, etc.
At the same time, we've been looking for a hacker to help us with the (installable Mac, PC, and hopefully Linux) RescueTime client (as well as other startup duties, ranging from our API to helping with product strategy). We've looking at local Seattle folks as well as remote people in nearby timezones.
We have some good candidates, but I've been struck by how FEW fit the YC hacker mold...
So, out of curiosity-- does the idea of writing client software appeal to anyone in the Hacker News demographic? This isn't a plea for candidates-- I'm more curious if people find the idea of writing client software appealing anymore.
(
57 comments
| 36 points
| on HN
)
Also, the knowledge required to deploy apps to each of your target platforms are fairly different, and tend to be developed to the exclusion of each other. A great Mac OS software engineer is unlikely to know Windows inside and out, and a Windows guru isn't likely to know or care much about Linux. Linux folks are, well, an altogether different bunch.
I really don't think there are many web developers that can pound out an interactive web GUI with the speed that I can bang out a cross-platform desktop app with a reasonable toolkit. There's a natural bias here towards web apps since this is a web-app community, but there are a lot of great developers out there that like working on desktop stuff.
@webwright -- feel free to contact me. I know a lot of people from the KDE world that do cross-platform apps; I could try to put you in touch with some people.
That being said, I don't think it's fair to argue that desktop apps are easier to develop, test, and deploy than their online counterparts. Furthermore, information-sharing features that are trivial to implement via the web can be rather more complicated to build into a desktop tool.
To tie this back to the original topic: great desktop hackers can throw together desktop apps quickly, and know the quirks for developing cross platform (just like great web hackers know browser quirks). In contrast to most of the crowd here, I'm pretty darn good at desktop (and server / systems) programming, and mediocre at web programming, so I just see the other side of the coin.
That said, I've been thinking about XUL/Firefox addons for some simple configuration things.
If you value your sanity, put the XUL handbook down and step away slowly. Of the handful of completely failed software projects I've worked on, most have involved XUL and the Mozilla runtime stack in some major way.
The complexity of XUL isn't worth it for the payoff, IMHO. Stick with something simple like Shoes or Tk, or go for Qt or WxWindows if you need a rich widget set. Don't let the fact that XUL looks kind of like HTML mislead you into thinking it'll be easy to build on and deploy.
http://www.trolltech.com/
I guess the web is what's hot right now (and that's hardly going to change so quickly) so it's what attracts the freshest talent. I don't think there's anything fundamental about web technology that will attract "YC style hackers". I also don't think the desktop is dead just yet.
I suppose it's therefore no surprise that my own pet project is a kind of web/client hybrid that you'll be able to use either via a browser or run locally. (although some of the more complex graphical UI is pretty tricky to do in a browser, so we'll have to see what happens)
I'm probably in the wrong country to help you out directly, but I suspect there are plenty of people out there that fit your requirements. I don't hang out there, but you could check the Joel on Software boards/jobs, I understand that's frequented by Windows folk.
EDIT: this post seems to make me sound old. I'm 24, so typical YCer age, as far as I can tell.
to add on: this is why i'm very happy with .NET. the overlap between web apps in ASP.NET and client based apps is large. no mac or linux, obviously. recently i've started building a small windows app again, and i've been so pleased by how quickly and smoothly it's been - even though it's been years since i've worked on a windows app.
when i first saw this post title - i instantly thought in my head, hey - doesn't rescuetime do that?! i absolutely love their product. i'd work for them in a heartbeat if my skillz were better.
i don't think client-based apps are dying, at all. if anything, rescuetime is showing that they are on the rebound. good work, guys.
To elaborate, the pool of people willing to pay for Linux client software isn't large enough. The pool of people willing to pay for Windows software is large enough, but I don't enjoy writing C#/.NET or MFC. And as importantly, it is hard to stick out as an indie in that environment.
So, the time invested to learn these technologies isn't worthwhile.
On the mac, you have a user base which is used to paying for software, and it is growing. And although no environment is perfect, I do enjoy writing Objective C and Cocoa.
But that's not the truth. I've been doing desktop stuff for years so it comes naturally to me, whereas web stuff is new. The people you are meeting here grew up with web stuff, not with desktop stuff.
It's just another marketing/sales numbers-based decision. If I had an app that targeted MS Office apps, for instance, I wouldn't have a bit of a problem writing it on the client.
I'd take it a step further. If I had an app that took a minute to load the first time over the web, I'd seriously consider just targeting the client and getting more bang for the buck.
The reason some folks stay on the web is that people don't want to wait to use anything. If you can show them a working app they can play with in under 5 seconds, your click-through and sales go up. You can't do that with client apps.
Nothing special about web or client, it's all just a numbers decision (or at least, it should be)
However... yeah, doing client apps is not "where it's at" compared to web apps. I never thought I would say that. Web apps were, once upon a time, sort of ugly and boring compared to all the cool stuff you could do with 'real' apps. But with things like Rails, and the ability to easily deploy new versions, the world has changed, and web apps are "where it's at", in a lot of ways.
If you're interested in using Tcl and Tk, I could send out a few feelers to that community. Lots of them aren't really in the YC 'demographic' (older, families, etc...), but some of them are pretty sharp coders.
The same is true about web interfaces, of course, but they at least have hype behind them, and therefore they're picked up by trendy young coders. Plus, there's the challenge -- or, IMO, endless pain -- of actually making it work across multiple browsers.
There is certainly an art to making a good, usable interface, but it's not a typical programmer's challenge, and writing a UI by hand is simply a pain in the ass. It sucks to do the stupid connections and packing if you don't have a drag and drop layout tool. And once you have that, you start leaving the programmer's domain, and into the designer's domain.
Note, I'm only talking about interfaces. The logic behind them can be anything, but it's the same logic with a web or desktop frontend.
I think it's just that once the shine wore off of the "hey, I can make buttons!" thing, the highly motivated programmers realized that UI design wasn't something that they wanted to focus on -- it's better left to designers (in theory at least -- im reality it's probably left to lowly grunt programmers) who can make the UI with drag and drop GUI builders, leaving them to work on interesting technical challenges. Making a GUI tends to be incidental to the core of the problem. I suspect that if it wasn't for the shine factor in web apps, it would have the exact same sort of apathy that you see in most programmers about desktop GUIs.
Oh, so very wrong. Yes, technically, the mechanics of making a GUI are not hard, but it's much like good technical writing. Deciding what goes where, what goes in, what stays, out; these are hard choices. Just look at almost any random shareware VB app. Fugly.
Most coders simply aren't meticulous enough when it comes to interfaces. "Slap a button on the window" or "just throw an item in the menu" without thought are not usable solutions.
This is especially problematic in client-side software where marketing is only interested in bullet-point features. The accessibility and workflow behind these features tend to be suspect at best, downright unusable at worst.
I wish more coders would be interested in these things. The people I talk to about interfaces are either disinterested hackers who'd rather work on backend code, or artists with no conceptual grasp of the technical underpinnings of GUI. Ugh.
It's not like mechanical engineers spend the majority of their time deciding on the trim and positioning of internals which compose the interface to the car. Instead they collaborate with the designers the constraints on the interior layout, and then they leave the interface details to the designers, while working on the drivetrain, suspension, frame, and so on.
The point I'm making isn't that GUIs are unimportant. The point is that GUIs are uninteresting if you are looking for a technically challenging problem to solve with code. This lack of challenge can be compounded today with the trend towards designers providing specs to programmers, and then leaving the programmers to implement it, as the creative element is reduced.
I wish it were true for web interfaces... something like balsamiq.com, but it would output html (or haml, etc.) instead of xml.
the turning point for me, where i decided that i wanted to focus more on web dev type things, was in a UI and software engineering class i took in college. we had to build a c/c++ program to process and display some data graphically, with a nice gui interface.
learning about, creating, and working with a modest GUI was painful and time consuming, to say the least. everyone struggled, and what took my group (4ish people) weeks in c/c++ and MFC would've taken me hours with html/javascript. the productivity difference and learning curve totally turned me off of client-based app work.
having said all of that, i acknowledge that i didn't do work in .net or in a java framework, and i know that the situation is currently much better than it used to be. i'm not claiming that one is better than the other, just explaining why i turned my focus away from client-based apps. i'd love to return to them, just haven't had the need or time to do so.
also, full disclosure, i dropped rescuetime an email about employment a while ago :)
Many such programmers are burned out or just laid off, so they will consider working outside of games, but you have to bait them a little so they know you're not a corporate dullard. I would suggest a job listing with some game-programmer keywords or even sneaking onto CreativeHeads or Gamasutra.
I say this not in an exploitative mode, but because that was my profile when I jumped from games into a job as a 2000-era dot-com client software programmer. They specifically mentioned that they were looking for console programming experience because there were several former game programmers there who understood this dynamic. And I was quite happy with the time I spent there.
I'm not planning on making a career out of client software, but I do enjoy it at times. I strongly prefer writing web apps, but I also hack away at OpenGL and C++ occasionally in my spare time.
I believe the greatest measure of an application is the user's productivity, and I believe most of that productivity is inherent in the design of the user interface. The users of each platform have different expectations of their user interface, however, so I believe it's my duty when developing cross-platform applications to be mindful of these expectations.
The work may seem unglamorous to most programmers, but if you can't get the human half of the interface right, any gains on the computer half of the interface are moot. That being said, I think most YC hackers do have an appreciation for this logic, it's just that client software is overkill for their requirements.
I'm sure some day I'll love Client Apps again, maybe when Microsoft isn't killing the little guy.
So in short, make sure you do several usability studies with people who fit your market segment.
As a matter of fact, I fixed the Status Item icons for RescueTime (to match the standard icon style) just the other day because the ones that came with it bugged me!
Here you go!
http://djork.net/rescue/RescueTimeMenu_off.png
http://djork.net/rescue/RescueTimeMenu_on.png
By the way, I've always wondered--is there a feature in your product that monitors how often you mention RescueTime on news.YC and elsewhere? If there's not, or if it's not automated, you should add it. That way at the end of the day, you could see how often you've namedropped your product (as a measure of success). I'm only half-kidding. :)
http://www.google.com/search?q=site%3Anews.ycombinator.com+r...
Looks like 66 of the 481 pages with the word RescueTime somewhere on them have my username somewhere on the page. I imagine many of those are assorted duplicate views of the same comment and many more are threads where one person mentioned RT and I responded.
Feel free to sort thru the times that I've mentioned RescueTime to see if I meet your obviously high standards for contributing to the community.
Being a troll and finishing with a ":)" doesn't really make it okay.
:)
Besides, anybody who actually goes to MSDN conferences and hacks the windows API is probably on the corporate dole and would never be so dumb as to try starving/start-up.
On the upside, if everyone around here was still obsessing over client software, somebody might have beat RescueTime to the punch! :)
I can (and do) both web and Mac programming, but don't live near Seattle. Of the 2, I prefer Mac programming.
I can't speak for Windows or Linux client development, but most of the Mac developers I know are running (or want to start running) their own indie Mac software shops. So you might want to find some quality Mac software contractors (I know a few).
I for one don't like to write web applications (mainly because the technology fragmentation), and I prefer to use client application whenever I can.
Having say that I can't see myself writing Win32 API as a day job in the near future, for all the reasons mentioned above.
Right now, I'm working full time doing PHP and I want to keep the job stability even with that slow language, so sorry, too late.
Yes, those people exist, it's just not trendy to write lower-level OS-specific software these days. Maybe it never will be again.
Cross platform, deployable on the web or any OS desktop, or mobile phones (with new generation browsers)... yes.
But we had to write an entire framework first ;)
And I like wxWidgets. So, sue me.