We thought hard about an actually useful finance app on this very limited smart watch, discarding any accounting or similar beacause input using three buttons is too cumbersome if you have a mobile phone in your pocket a few inches away.
We ended up creating a watch app that showed you the route to the next ATM on a map, along with a description of the route. Technically pretty challenging since we had to generate map tiles on a remote server and load them onto the watch. Also, each image had to be sent in two chunks since the transfer buffer was smaller than the screen...
Another group just assumed the Pebble had a camera, color display and a microphone and had no demo, just a power point presentation. They ended up as winners...
My pet peeve was always make the event more about "the hacker experience" and less about "the best PPT wins".
Things we did:
* PPT-free event: a team must show something working.
* Startup teams trying to pitch an already working product were kicked out.
* Each team must name one PR member, mentors and other staff should not interrupt anyone except this PR guy.
* Ingenuity and implementation completeness were the main criteria (the least mockups the better).
* Zero tolerance for antisocial behavior.
We strive a lot do make sure "the best hack" wins.
1. A team winning a few very significant awards (including second place) for pitching an app that allows you to take picture of your food bowl and tell you the nutritional content breakdown. Of course no demo was provided, and the guys fessed up that they "didn't know anything about machine learning until two days ago, but learned everything needed to make it work in that time period." No one questioned authenticity or whether it was actually a possible thing to make.
2. Another group of 10 people who ONLY made a powerpoint talking about some app that mixed traveling and tinder. When asked by judges whether they had something besides powerpoint, they said that they "are not coders, but idea-people", and that it took 10 of them to make that powerpoint.
Why didn't you call them out on their bullshit?
Along the same lines, there were a few local meetups where people were going to plan some ideas for innovative uses for public data sets, and what kind of data we should try and get released from the city & county. The whole thing ended up getting de-railed by non-tech "thought leader in a turtleneck" consultant types giving their personal pitches to market their brand, and nothing solid came out of that. Those who were interested in building something formed a separate group and went their own way.
At the risk of sounding like a delicate snowflake, I would really enjoy more "tech events for people who really want to get their hands dirty".
A lot of small local game jams fall closer to the second category there. I think you are right that financial stakes affects the attitude of the hackathon.
Most of the teams came with something pre-made and tried to fit it to the theme of the event. And one team was pitching their startup. Of course all of them were good at pitching, but implementation-wise they were ahead of "hackers" too even not touching their keyboards...
My friends are both pretty darn good software engineers, and went to pick up some other floaters to build a team there. They got a project manager, who they tasked with finding them more engineers. Project manager comes back.... with 2 more project managers. So with their team of 2 engineers and 3 project managers they got very little product done.
I think events like this shouldn't be called "Hackathons." Maybe "Pitch Events" or something. If you can win without writing a single line of code (which I have seen at two SF "hackathons") it should not be a hackathon.
Why? Just ignore the PM and get work done, just like normal.
PMs are great at hackathons for getting your drinks, talking to other teams, talking to judges and organisers about stuff they are looking for, getting the presentation ready.
So really the problem is the 3 other people on their team were just straight up incompetent / unmotivated, not so much that they were of X_Y_Z career.
"Build it and they will come" is a Hollywood myth.
We didn't win. Obviously, I'm biased, but I think our product was more promising both in terms of realistic use of the technology, and in terms of the possibility of going to market quickly. But our demo wasn't as shiny, we were from a remote office so people didn't really know who we were, and neither of us were particularly charismatic presenters.
Presentation matters. This has been impressed on us repeatedly; the joke is now that whoever manages to snag the UI/UX person first for their team is going to win.
I get the same feeling often when reading papers. It feels like the abstract and first few paragraphs hold great promise and then you get down to what the authors really did and it's like "are you kidding?" So often there is a big hype/substance mismatch.
But is there really another way?
However, it goes deeper than that as not even all developers (myself included) are always as good at evaluating technical merit as we think we are - particularly if the solution involves a lot of math.
So they judge it off an idea. Does the idea sound cool?
I usually go to get in the zone with some new technologies around like minded people, and not really about the theme of the hackathon itself. A lot of hackathons have tons of tertiary prizes and networking opportunities.
Unlike other places with a tech scene, Silicon Valley has an industry that caters to unskilled and wannabe programmers that aren't currently into programming at all. Hackathons, Meetups and the coding schools are at the center of that. So you shouldn't expect actual deep technology discussions at those particular things, you will be underwhelmed.
It was really disappointing. Maybe it was just that specific hackathon? I knew "the pitch" was a big part of winning, but didn't expect it to be 99%. A few teams built some actual cool and functioning things in 24 hours. Ours was the only app with a real demo you could visit/download, rather than it only working locally on the dev's machine. But the only teams that reached the finals were the ones with great speakers and a good idea, even if it wasn't functional at all.
The guy I know ended up winning the first prize at that event. His team had an amazing idea and a great pitch, but their "app" was a powerpoint presentation, and a couple static HTML pages that faked a dynamic user flow. It worked as long as you clicked the correct image map area, and entered values into text boxes that matched what was hard-coded into the next page.
I had fun with my team and made new friends, but it was really discouraging to lose a "hackathon" mostly because the other team had better speakers and not for technical reasons. I guess I prefer game jams, no qualms about marketability or a pitch with empty promises. Maybe it's because game jams usually don't have financial prizes aside for the exposure?