Challenge ends soon!
Submit your entry now
DevCycle Feature Flag Challenge
Always Know the State of Your Flags!
We are so excited to team up with DevCycle to bring the community a challenge all about having fun with feature flags!
Running through December 08, the DevCycle Feature Flag Challenge provides an opportunity to think outside the box by getting creative with feature flags. If you've only used feature flags for release management or A/B testing, prepare to unleash your creativity and discover their playful potential. Think game mechanics, interactive experiences, or even generative art – the possibilities are endless.
Prizes
We have one prompt for this challenge but three ways to win.
Overall Prompt Winner (1)
- $500 USD
- 6-month DEV++ Membership
- Exclusive DEV Badge
- A gift from the DEV Shop
Additional prize category Winners (2)
- $250 USD
- 6-month DEV++ Membership
- Exclusive DEV Badge
- A gift from the DEV Shop
Good luck and happy coding!
Sponsored by DevCycle
DevCycle is a feature flag platform built for teams of any size, helping you easily create, rollout, and cleanup feature flags without disrupting your workflow.
Key Dates
- Contest start: November 27, 2024
- Submissions due: December 08, 2024
- Winners announced: December 12, 2024
Badge Rewards
Find Out More
Ask questions and share your ideas on the DevCycle Feature Flag Challenge Launch Post.
View Launch PostChallenge Prompt
Feature Flag Funhouse 🎉
Build an app that showcases the most unique, creative, or fun way to use feature flags in an application by leveraging a DevCycle SDK, OpenFeature Provider or the API! Feature flags are great for toggling things on and off, but this challenge is about exploring how they can bring your app to life in more fun and imaginative ways.
We have two additional prize categories for this prompt:
- OpenFeature Aficionado: Awarded to a project that showcases the most creative use of a DevCycle OpenFeature Provider!
- API All-Star: Awarded to a project that shines by making full use of the DevCycle API— showcase creativity and capability through effective integration!
How to submit
In order to participate, you will need to publish a post using the submission template provided.
All submissions must implement a DevCycle SDK, OpenFeature Provider or the API, and have an MIT license.
Judging Criteria:
- Use of underlying technology
- Usability and User Experience
- Accessibility
- Creativity
- Additional Prize Category Requirements (if applicable)
DevCycle Feature Flag Challenge FAQ
Participation
Can one submission qualify for multiple prize categories?
Yes, if your submission offers a solution to multiple prize categories, it can qualify for multiple prize categories.
Can I submit to a prompt more than once?
Yes, you can submit multiple submissions per prompt but you’ll need to publish a separate post for each submission.
Can I work on a team?
Yes, you can work on teams of up to four people.
- If you collaborate with anyone, you’ll need to list their DEV handles in your submission post so we can award a badge to your entire team! Please only publish one submission per team.
- DEV does not handle prize-splitting, so in the event that your submission wins the shop gift, you will need to split that amongst yourselves. Thank you for understanding!
How old do I have to be to participate?
Participants need to be 18+ in order to participate.
If I live in X, am I eligible to participate?
For eligibility rules, see our official challenge rules.
Submission
Can my submission include open source code?
Riffing on open source code and borrowing and improving on previous work/ideas is encouraged but it’s important your changes are significant enough to ensure your submission is valid.
When does riffing become plagiarism?
It will depend, but transparency is important, license compatibility is important. You can use someone else’s code to give you a jumpstart to demonstrate your ideas on top of someone else’s base, but not just re-package the base. It should be clear to the judges what you added to the project in terms of the code and conceptual inspiration. This means, you should clearly state what you were building on and what elements are original to this new submission. When building on existing code, we expect a significant change that adds something tangible to the output. i.e. a new animation, and new sprite, a new function, a new presentation. Not just changes to the source - i.e. changing colours, changing one sprite, changing one function.
What happens if my submission is considered plagiarized or invalid?
Anything deemed to be plagiarism will not be eligible for prizes. Incidental plagiarism may simply result in your disqualification from the challenge (regardless of the number of other valid submissions you have published). Egregious plagiarism will result in your suspension from DEV entirely. Any non-generic, non-trivial usage of prior work, including open source code must be credited in your submission.
Do submissions have to be in English?
Non-english submissions are eligible for a completion badge but not eligible for prizes due to the current limitations of our judges. We will not be judging on mastery of the English language, so please don’t let this deter you from submitting if you are not a native English speaker! We hope to evolve this in the future to be more accommodating.
Do I need a license for my code?
Yes, you are required to include an MIT license to your code.
Can I use AI?
Use of AI is allowed as long as all other rules are followed. We want to give you a chance to show off your skills in realistic scenarios. If you use AI tools to help you achieve your submission, all the power to you.
How do I embed my project directly into my DEV post?
Our editor supports many types of embeds, including: Stackbliz, Glitch, Github, etc. You can typically use the {% embed https://... %}
syntax directly in the post. Click here for more information on our markdown support.
- For CodePen, you will need to use this syntax:
{% codepen http://... %}
- For CodeSandbox, you will need to use this syntax:
{% codesandbox http://... %}
Judging and Prizing
Can there be ties?
In the event of a tie in scoring between judges, the judges will select the entry that received the highest number of positive reactions on their DEV post to determine the winner.
How will I know if I won?
Winners will be announced in a DEV post on the winner announcement date noted in our key dates section.
When will winners receive their Forem Shop gift?
The DEV Team will contact you via the email associated with your DEV profile within, at most, 10 business days of the winner announcement date to share the details of the shop gift.
When will I receive my DEV badge?
Both participation and winner badges will be awarded, in most cases, within a week of the winner announcement.
When will I receive my prizes? The DEV Team will contact you via the email associated with your DEV profile within, at most, 10 business days of the winner announcement date to share the details of claiming your prizes.
What steps do I need to take to receive my cash prize?
The winner (including each member of a team) may be required to sign and return an affidavit of eligibility and publicity/liability release, and provide any additional tax filing information (such as a W-9, social security number or Federal tax ID number) within seven (7) business days following the date of your first email notification.
DevCycle Feature Flag Challenge Rules
NO PURCHASE NECESSARY. Open only to 18+. Contest entry period ends December 08, 2024 at 11:59 PM PDT. Contest is void where prohibited or restricted by law or regulation. All entires must be submitted during the content period. For Official Rules, see DevCycle Feature Flag Challenge Contest Rules and General Contest Official Rules.