Join LaunchKey and start your Hackvember right. Build something amazing or just plain fun with LaunchKey. Every submitted entry wins a prize. The best entries win additional prizes.
Have fun and meet other developers in the Las Vegas area while utilizing LaunchKey, a passwordless decentralized authentication and authorization platform. Form a team and build a solution utilizing authentication, authorization, or both with one of LaunchKey's SDKs for Android, C#/.NET, iOS, Java, Node.js, PHP, Python, Ruby, or Windows Phone.
Cash* prizes will be awarded to the best implementations in both authentication and authorization as voted by the LaunchKey judges as well as a people's choice award voted on by the crowd with the LaunchKey mobile app after the presentations are completed.
The event starts at 10 AM with an overview of LaunchKey and introductions to the LaunchKey staff that will be providing any assistance you might need with your project. Feel free to show up a little early to get situated and network with your fellow hackers.
Lunch will be provided as well as drinks and snacks.
*Cash equivalent in gift cards may be used in lieu of actual cash.
- Participants: Individuals of any age may participate and submit an entry. All participants must be on-site at the event. No remote participants will be allowed.
- Teams: Teams of up to five (5) may submit an entry. A participant submitting an entry alone will be considered as a team of one (1). Participants may only submit as a participant on one (1) team.
- An original work that interacts with the LaunchKey Engine API either directly or utilizing a LaunchKey SDK.
Performs an authentication or authorization request as part of the logic flow of the application.
- Demonstrates the logic flow during a live demonstration before the judges.
How to enter
Attend the hack-auth-on and submit an original work that was fully completed at the event.
Yo Sub Kwon
LaunchKey Founder/VP Engineering
How well does the solution utilize LaunchKey? Did it utilize Server Sent Events (SSE) as opposed to polling. Did it utilize context in the request?
How innovative was the solution? Did it expose a unique use case? Did it provide a new solution to an existing use case?
Was the solution secure in its implementation