Posted on 01-08-2012
There are a lot of reasons for throwing a hackathon, and what value you get out of a hackathon will vary depending on who you are.
As I explore the hackathon phenomenom in 2012, I’m trying to track on what value hackathon organizers, API owners, mobile platforms, developers and other participants get out of hackathons.
I will be tracking on the different reasons people attend hackathons throughout the year, and share my findings, but here in January I know one thing for sure--hackthons are a marketing vehicle. Whether you are the hackathon organizer, an API provider or developer you are depending on the event to market your organization, business, API or talent and skills as a developer.
In future posts I will write, more about the marketing effect of hackathons, but I wanted to talk about a common mistake I’m seeing from hacakthon organizers--no Twitter hashtag for the event.
A Twitter hashtag is probably the most important marketing element of your hackathon. It should be everywhere, on your site, print materials, slides...everywhere. A hackathon organizer should be tweeting out every aspect of the event with the hashtag, before, during and after the event.
The hashtag will enable sponsors and other participating businesses to market themselves around the event. It will also allow hackathon developers to showcase their ideas, skills and applications.
While researching hackathons I have to spend a lot of time tracking down the event hashtag, and many times I have to ask an event organizer to provide it, and often there isn’t even one.
If your organizing an hackathon, make sure and establish a unique Twitter hashtag for event right away, and use it everywhere, everyone involved will benefit, and your event will be much more successful.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems