After joining angelhack, I identify some useful skill sets for hackathon.
Technology
The mission of developer in hackathon is to make software for presentation.
- UI and UX is everything, developer should put most effort on it
- Hardcode everything
- If it can save development time
- If it can make the presentation more smooth
- If the computation is slow, just hardcode it to make it fast.
- Forget everything about backend
- Because it cannot be ‘seen’ by judges
- Learn to use prototype tool and API before hackathon
- This help us build good looking and ‘functional’ prototype.
Design
User Experience and User Interface is the key point. It is the visual content for judges
- Interface need to be clean and simple, it helps judges to focus on the feature you are going to present.
- The operation should be intuitive enough, judges should be able to use it without learning.
- Save time on explain how to use in pitch
- It is wasting time to explain “We click this button to perform bla bla bla…” to judges
- Save time on explain how to use in pitch
Pitch
Presnetation time is too short. Squeese the speech to maximize the value of every word you speak.
- Don’t waste time on saying anything cannot add value to the product.
- such as team introduction
- User Story may not be very useful
- Time is too short for demonstrate your product after provide a user story
- Present your idea and demonstrate your prototype at the same time
- Use one or two sentence to explain your idea
- Your idea must be simple and well-known.
- The idea can be solving some simple problems in daily lives
- Your idea must be simple and well-known.
- One member demonstrate the usage of prototype
- The UI/UX of prototype must be clear and simple
- Another member explain the function and idea of the prototype
- Use one or two sentence to explain your idea
- If your prototype is using some common technology, technical part can be skipped
Product design
In the aspect of engineer, we are always focus on problem. We identify the problem and then find out best solution to solve it.
But in businuess, it is not the case. Even you solution is perfect, the client may not use them. Some client don’t think a problem is problem, they may not want to solve it.
To design a product, we can focus on what do user need. Sometimes, client is not paying to buy an object, but some abstract values or feelings. For example, some people spend lots of money on online games not because they enjoy the game, they may just want to show off and beat other player. That is the feeling the client want to buy.