The source code (for iOS, at least) is also pretty clean and decently commented for what it is.
$96k is still outrageous, but for work-for-hire it's off by a factor of 2-5 rather than a factor of 10.
Nevertheless, it's crap. The quality of the constructed software is irrelevant because the feature set is a no-op. It's a graphical front end for a NOAA web service that returns temperature and humidity. If the public isn't living and breathing the content of that NOAA web service, maybe it's because there's no graphical tool to access it, but maybe it's because they have 50,000 other ways to determine temperature and humidity at their current location. Like, say, existing in a conscious state at their current location.
Most of us can say "it's cold" or "it's humid" -- but we rely on more mature data services so we can know exactly how cold or how humid it might be...
You've essentially just argued that NOAA stat tracking is pointless because "you can stick your head out of a window".
I've argued that the translation and re-display of these particular NOAA stats on a smartphone, for the viewer's location, is pointless because I can stick my head out of a window.
When operating an aircraft, I love NOAA stat tracking. I think NOAA and the National Weather Service are probably two of the best deals the American public can ever expect to get for their money.
I know with my work, when we're doing construction contracts with the municipal governments we charge at least double and we're the most expensive in the area to begin with (we have guys who've been employed for 20+ years, rather than guys who've been employed for the last 9 months). So I'd say it's probably on-target for a government contract.
> Like, say, existing in a conscious state at their current location.
Or perhaps the free app that comes as standard on an iPhone is why people aren't using the NOAA web service.
Although I know I prefer the Weather Office info here in Canada as it's more accurate and local than The Weather Network, which is paid for. It just doesn't have as many gimmicks, but then they don't whore you for adverts by being inaccurate enough to keep you checking back.
How do you know what code to write in those 6 hours? How did you even know there was an opportunity? What are the requirements? Is there a spec? How is the customer assured you are capable of delivering what they need? Does the customer even know what they need? Is what they _think_ they need even possible? How will you prove you've delivered what they asked for? Is there a need to user acceptance testing, and if so who's going to write the tests and who's going to do the testing? Are there any safety/copyright/legal implications about what the software displays? Who's ultimately responsible for those? Who need indemnifying or insurance to cover that? Is there any backend service required in addition to the mobile app? Who's building/maintaining/paying for that? Who's responsible for "fixing" the app if a 3rd party backend the app relies on changes or goes away? Does the customer require copyright ownership of the app source code? Are there 3rd party licenced libraries you're going to use that you don't have enough rights over to be able to give/sell the copyright to the customer? Who's going to spend the time figuring out and explaining to the customer exactly which bits of the source code they do and don't own? Are there any patent issues relating to the problem being solved? Are you _sure?_ Who's "on the hook" for patent infringement if something comes to light later? Who's doing the UI/UX/graphic design? How many iterations through the customers approval process will need to be done? What are the customers turnaround times on those approvals and who at the customer has the authority to ultimately sign off on things? What documentation is required? Who's writing that? What training is required? Who's doing that? What ongoing support is required? Who's doing that?
I think sometime developers fail to understand just how much _business_ stuff needs to happen before and after they write their code. It wouldn't surprise me at all to find that in the _best_ case, a project like this with "6 hours of development" also required 4 or 5 times as many hours to get the deal done. I could also very easily see the team stalled for a week or two waiting on approval/signoff, and if your 6 hours of development turns into two weeks where you (or a colleague) couldn't do other work 'cause you're chasing answers, decisions, or approval from the client - a factor of 10 between the "actual coding time" cost and the project cost starts to seem positively reasonable.
Or do you honestly think 6 hours worth of coding @ $100/hr is all a job like that requires?
Have you ever worked with a government department?
I couldn't help but note that the title contains Useless Android Application, although the article indicates that the total cost of $200,000 was spent on Android, iPhone and BB (not completed) versions.
I won't go as far as calling it linkbait, but if I ever wrote an article about an app I didn't like and it was available on Android, I now know a way to get more traffic if I were to submit to HN.
I'm having a hard time feeling outraged over the extra 0.06 cents this is going to cost me and every other American. It's all 'fail early, fail often' here on HN until the government does so, then failure and experimentation are considered intolerable inefficiencies.
This particular project seems like a bit of a miss, but even simple statistics can be enormously useful for some people: http://explore.data.gov/catalog/apps/
I don't _want_ my government to fail early and fail often. I don't _want_ them to experiment. I want stability, I want them to be on this side of the bleeding edge, I want them to be a generation behind.
When a startup takes this approach, the risk v reward is shared between the few people who sat down and decided that risk is worth taking. When the government does it, that risk is shared amongst the entire country, many of whom never wanted and could never benefit from the reward. Are government smartphone apps a useful idea? Why sure they are. I'd be willing to put my tax money towards the development of technologies that can improve my life. But I'd like them to be worth the money. Not sometimes, but _every_ time, or at least damn close to every time.
What I'd really rather see is the government investing in an open API for their tools and information and letting the private developers wrap around them, presenting the information in a way that is useful to a wider variety of people. The developers stand to make money from the $0.99 sale of the app, and the government gets to have the information available to the people who need to see it.
Right now my transit authority runs a halfway-decent website along with a freely accessible API. The website is functional, but not perfect. There is a thriving market for people who can present the same data in much more usable ways, for profit. This seems ideal.
What you're suggesting is that the government never engage itself in building frontends - and stick strictly to building data backends instead, and leaving all the gooey UI to private industry. In other words, people will no longer have free access to census data, bus schedules, budgets, or anything. Well, unless you're a geek who knows how to figure out the documentation to the API, craft some API calls, and parse the results into some human-readable form.
I can't think of a worse techno-dictatorial dystopia. The only people who gain freedom are the geeks, everyone else loses free access to their own government's data unless they cough up the cash.
I didn't really mean "that the government never engage itself in building frontends", I meant that the government, at this point, refrain from building smartphone apps. Until the app market is as standardized and established as the web, it will always be a waste of money to build apps for one platform, and a money sink to include them all.
Sorry for the miscommuication.
It's not as if publishing a smartphone app is exactly "bleeding edge" these days. Third party smartphone apps have existed for almost four years now.
My point is - I fail to see how this is an issue with the government trying to pursue "too much innovation". This could have just as easily happened with an overpriced website contract, but I doubt we'd be sitting around arguing whether or not governments should publish data on a website!
It's not the job of the government to innovate, it's the job of the government to function. I don't install Ubuntu 12.04 Alpha on my production servers, I install 10.10 LTS.
And there is probably a lot of other stuff involved that I don't know about. And lets not forget some overhead to pay for the office and some profit.
It probably ends up being a few hundred man hours once you account for everything.
So yeah - it could most likely be cheaper or better, but the pitchfork attitude is probably going too far.
I am a professional Android developer. Something like this wouldn't take more than a day. It's a piece of cake.
What I suspect happened here is that the project was outsourced. These silly people tried to save money by hiring a foreigner to talk to another foreigner developer and get the app developed. To work on and a deliver a product these foreigners know nothing about.
A little while ago I had a little financial situation and was forced to take some cheap freelance projects. I was quickly picked up by a foreign recruiter and I took a couple of jobs really cheap. At the rate the Indian developers would charge.
I had to work on an app that was commissioned by CAT. The app was a paving calculator that was to be used by their employees.
This was seriously some of the worse source code I have ever seen.
I took my own personal time to rewrite the project. I also redid all the calculations and found various mistakes everywhere. I asked them to send me all the docs and had to redo everything from the ground up because these people were plain incompetent.
For about a couple weeks work I charged $300 dollars. I didn't care about the money, I just didn't want any of our road workers using a shitty and potentially dangerous application.
Correct results are absolutely critical in any non-trivial application. Acceptance of incorrect results just shows how low the quality grade is.
FYI, I'm looking at the source, and it's pretty basic. Nothing a high school student couldn't write.
It looks like the company that made this was: http://pixelbitcreative.com/ also: http://erg.com/
Lol, they don't even have a real site yet they specialize in Web Development. What a joke.
Bad developers exist everywhere.
To you, the American were foreigners which further enforces my point that working with foreigners in an issue.
I'm not saying that because I'm American my code is better. I'm saying that because I'm local and I care more I produce better quality.
BTW, in my story some of the most incompetent people were indeed American. The other developer did the best he could, and the recruiter too. The process was broken from the beginning. They wrote really bad documentation, and incorrect formulas. The source was bad, but it took much longer to get all the formulas properly documented and figured out.
There's no evidence to suggest that this application was off-shored, unless you've found something to the contrary. Quite clearly, the two companies you cite are located in Massachusetts and Virginia and both companies are staffed by developers in the US.
I suspected it was offshored because I smelled the rot, but looks like I was wrong. It was just the victim of the broken process.
That's what my rant is really about, not necessarily against foreigners. It's just that the process produces broken/poor software.
I'm not saying that it's true for every company, but it was true for CAT.
You should have contacted CAT directly and upsell them exposing their blatant mistake.
Even if you were to divvy that up evenly, it would make the implementation 10% of the cost.. about 10k.. which is pretty cheap on a "work for hire" basis of a software house for a software developer.
Now I look at this, it's actually quite cheap !!
Also... the contracting process is similar to what he describes anyway, in fact it is better. For example [SBIR](http://www.sbir.gov/) (I hope hn uses markdown) are small business requests for R&D on everything from software to engineering. A small amount of $$ is given up front, and then more if the project becomes field testable, more if it becomes usable.
You didn't? Why do you think we need to make the switch to IPV6?
Ready? Go! Keep track of your hours...
I installed the app. It works fine. Responsive, fast, no problems. I have two minor quibbles with the design, but they are minor. Does what it says on the box. Not an exciting piece of software, but... Has even one person commenting on this thread installed it except me? No? Didn't think so. "It's a piece of crap" says a highly self-interested blogger, and Hacker News jumps on that like starving dogs on Alpo.