DEV Community

Cover image for Join us for the DevCycle Feature Flag Challenge: $1,000 in Prizes!
dev.to staff for The DEV Team

Posted on • Edited on

Join us for the DevCycle Feature Flag Challenge: $1,000 in Prizes!

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 8th December 22nd, 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.

We have one prompt for this challenge but three ways to win.

Did we mention how fun this will be? Read on!

Our 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!

Here is the submission template for anyone that wants to jump right in, but please review all challenge rules on the official challenge page before submitting.

Submission Template

Judging Criteria and Prizes

All submissions will be judged on the following:

  • Use of underlying technology
  • Usability and User Experience
  • Accessibility
  • Creativity
  • Additional Prize Category Requirements (if applicable)

The winner of our overall prompt (1) will receive:

  • $500 USD
  • 6-month DEV++ Membership
  • Exclusive DEV Badge
  • A gift from the DEV Shop

The winners of our additional prize categories (2) will receive:

  • $250 USD
  • 6-month DEV++ Membership
  • Exclusive DEV Badge
  • A gift from the DEV Shop

All Participants with a valid submission will receive a completion badge on their DEV profile.

How To Participate

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.

Please review our full rules, guidelines, and FAQ page before submitting so you understand our participation guidelines and official contests rules such eligibility requirements.

Need Inspiration, Feedback, or Help?

You can get to know DevCycle by utilizing their docs and tutorials:

We encourage all participants to join the DevCycle Discord Community to connect with their team and more developers implementing feature flags!

Important Dates

  • November 27: DevCycle Feature Flag Challenge begins!
  • December 08 December 22: Submissions due at 11:59 PM PDT
  • December 12 January 2: Winners Announced

We hope you enjoy the feature flag funhouse, and canโ€™t wait to see what you build! Questions about the challenge? Ask them below.

Good luck and happy coding!

Top comments (24)

Collapse
 
ben profile image
Ben Halpern

The last challenge was one of the most popular yet, excited to see what folks do with this one.

Collapse
 
schemetastic profile image
Schemetastic (Rodrigo) • Edited

What a cool idea! So, basically, it is like having variables in the cloud that you can manage and then in your code you can add the logic to test features, depending on the value that has on the cloud. ๐Ÿคฏ

Collapse
 
shafayeat profile image
Shafayet Hossain

If it weren't for all this study and work pressure, I swear Iโ€™d jump into this challenge right away. I really, really want to join, but I just can't right now๐Ÿ˜ญ๐Ÿ˜ญ๐Ÿ˜ญ

Collapse
 
jess profile image
Jess Lee
Collapse
 
ogbotemi_ogungbamila_3ad3 profile image
Ogbotemi Ogungbamila

I already found a fix. I had to experiment with common standards of authorizing API requests to find a way around the grave omission of API request parameters for making and viewing changes in the DevCycle API documentation - docs.devcycle.com/management-api

I will be sending a link to a gist containing a working code sample as well as mentioning this omission in my submission soonest

Collapse
 
ogbotemi_ogungbamila_3ad3 profile image
Ogbotemi Ogungbamila

Hello, I'd like to request for a sample API request code containing the body and headers required by DevCycle's API.
Their docs doesn't contain any hint at all for the API request parameters except for when obtaining an auth token at the start of the page.

Collapse
 
charliesay profile image
Charlie Say

lets go!

Collapse
 
jaisuryaprabu profile image
Jaisurya

All the best for all the participants ๐Ÿ‘

Collapse
 
pullreview profile image
Pull Review with Scott Beeker

Awesome!! ๐Ÿ˜Ž

Collapse
 
grunet profile image
Grunet • Edited

Not sure there's enough time to iron it out, but I thought of making a digital shishi-odori as a metaphor for automatic load shedding controlled by feature flags.

Collapse
 
jess profile image
Jess Lee
Collapse
 
jess profile image
Jess Lee

Good luck everyone!

Some comments may only be visible to logged-in visitors. Sign in to view all comments.