What to Build:

Build an app using the Twitter API v2 in one of the following categories and must also use at least one of the corresponding endpoints per category;

Content discovery apps

Help people discover content such as Lists, Spaces, Bookmarks, or Tweets, on Twitter. We have built an open platform that allows you to give people more opportunities to discover content that’s relevant to them. While we built some discovery experiences ourselves (such as the Explore tab for Spaces), people will benefit from alternative discovery mechanisms that can complement ours or be an alternative to them. Another element of discovery is the ability to create different perspectives of the public conversation. Our products enable you to build ways to filter content by a particular set of rules (for example, a specific topic), or to only surface content in a particular context (such as time of day). You can build tools to show relevant content based on those circumstances, such as apps that surface work-related content during the week, and fun content during the weekend.

Conversation safety tools

Help people feel more safe on Twitter. We want everyone to feel comfortable, safe, and excited to participate in the conversation on Twitter. We’ve worked hard to offer tools that give people more control over their experience, like Tweet reply settings, blocks, and mutes. However, there will always be more work to do, and we want to encourage you to build complementary or additive solutions that help improve the health and safety of the platform. For instance, apps that actively limit the content you don’t want to see/experience. Or filter unwanted content, mentions, and/or profiles.

Public good apps

Connect to real world issues, supporting people outside of the Twitter experience. We want to bring communities closer during real world events. Help people coordinate emergencies, tweet out vital information, or help people find assistance when they need it. Keep people safe and informed with tools to automatically share information like extreme weather updates, public health notices, or distributing information in times of crisis and more.

Check out the Categories tab for more information about the requirements for each of the categories.

What to Submit: 

• Provide a URL to your code repository for judging and testing. If private, please provide access to testing@devpost.com and chirpdevchallenge@twitter.com; be sure to indicate testing instructions within your submission.

• Include a video (less than 3 minutes) that demonstrates your submission. Videos must be uploaded to YouTube, Vimeo, Facebook Video, or Youku and made public.

• Identify which category you are submitting into.

• Provide Twitter handle associated with developer account. 

• Provide access to the deployed version of your app.