6 ms·
Honestly, if you asked these Rumble devs how many of them even tested in Firefox I think the percentage would be low. Such is the nature of these events - you m
by untog 12y ago
Honestly, if you asked these Rumble devs how many of them even tested in Firefox I think the percentage would be low. Such is the nature of these events - you move fast. And as the post says, the aim is to make an "innovative web application", not a "web application that would be delivered to users in an optimal fashion". It was also a Ruby hackathon - given that it's a server-side technology I doubt the client presentation form was given much focus.
I've made this mistake plenty of times before myself. I've dwelled on the the actual real life issues my concept would face and come away at the end of the weekend with a well-considered concept. But what people want at these events is a catchy, flashy demo that wows attendees and that can be tweeted/Facebooked/etc.
This is part of the reason I don't bother sacrificing my weekend to hackathons these days, but still. You're optimising for the wrong use case.
- jonathanstark 12y ago> But what people want at these events is a catchy, flashy demo that wows attendees and that can be tweeted/Facebooked/etc. And then what? Opened on a mobile phone where the demo doesn't work? Mobile is where people are reading facebook/twitter so if you want to optimize for catchy/flashy for sharing in social media, you should definitely focus on mobile-first.
- untog 12y agoYou're assuming the tweeted link would go to the app itself - it wouldn't. It would go to their roundup of the event. These events are not built around making long-lasting projects.