React Rally 2017 closed

Speak at React Rally 2017!

React Rally is a two day single track conference for developers of all backgrounds using Facebook's React. React Rally is on August 24th-25th in Salt Lake City, Utah. Speakers will cover topics such as React Native, Flux, ES6, isomorphic universal JavaScript, and so much more. Whether you're a seasoned developer who has been using React since before it was cool or a newcomer to the scene, React Rally has something for everyone!

What we are looking for

We want React Rally to showcase how the wider community is using React. We want stories about products or experiences that React made possible, stories about overcoming challenges with React, and ideas for solving problems that exist in React today. We are interested in hearing how you are pushing the limits of React, and how we can all use React to build better stuff. We want speakers of all experience levels and backgrounds, because React is for people of all experience levels and background.

Talks slots are 30 minutes long with no Q&A after. If you want to answer questions, let the attendees know in your talk that you will be available during or after the conference to talk. Q&A sessions can often devolve into one lone brave (or loud) person asking about a topic the speaker isn’t comfortable discussing or that the rest of the attendees are not interested in, so we’ll be skipping them.

You can submit as many proposals as you want, and you can edit them until the CFP closes. We promise not to peek. Of course if you buy a ticket and get accepted to speak we will reimburse you the ticket price.

Writing a good proposal

A good proposal serves two purposes. It demonstrates you have a story the attendees will want to hear, and it shows that you can present this story in an engaging and exciting fashion. To show that, we want a few pieces of information.

The first thing we want is the abstract. The abstract is the pitch to the attendees. It will appear on the schedule along with the title, and should tell attendees what they will learn from your talk and why they care about it. You don't have to give away all your secrets, but you should at least describe the main thesis of your talk. The abstract is limited to 600 characters, so make those words count.

The second thing we want is the details of your talk. This is more detailed information about how your talk will go down. Do you have an outline? What is the structure of your talk? How will you start? What will your conclusion be like? If you have live demos, how will you make sure they don't crash and burn? This information won't be made public. Also, if you don't know all of this when you propose, that is ok. Just give as much detail as you have.

The last thing we want is the pitch. This is where you pitch yourself as the the person capable of making this talk awesome. Why does this talk need to happen? Why are you excited about it?

Here is an example of an abstract, details and a pitch (this is not a good submission, just an example of one that includes the information we asked about).

Title: Semicolons are making your users weep

Abstract: How often do you type a semicolon? Did you know that every time you type that ";" character, a user of you app somewhere remembers the saddest thing that ever happened to them, and cries? Learn how to stop making your users weep sad sad tears, and become a better React developer in the process.

Details: This talk is an exploration of the etymology of the semicolon character of the terrible toll it imposes on our users. I will begin with a curated selection of my funniest kitten gifs to loosen up the audience. Then I will show 30 slides of a semicolon, growing slowly larger with each slide, as I repeat the words "Synergy. Radical isomorphism. Test-driven envelopment. Hyperlocal. Buttgeneering. Scale more by doing less." louder and louder. Once this reaches a crescendo, I'll unveil my new client-side JavaScript framework that is composed of only semicolons, and then ride off the stage on a chariot made of surveillance drones.

Pitch: Listen, every JavaScript developer knows that semicolons are the number one cause of loss of productivity. By accepting my talk, your attendees will improve their ability to deliver great experience to their users. I'm an engaging speaker who has been thinking about semicolons and literally nothing else for decades now.

So yeah, we probably would not accept this talk. But the proposal did give us a good idea of what it would be like.

How talk selection works

The CFP closes April 16th at 11:59 PM MDT. After the CFP closes, the speaker selection committee narrows down potential talks in two passes. The first pass is completely blind, with only at the talk title and abstract visible. The second pass adds in all the information you provide.

We will notify selected speakers within one week of the CFP closing.

Speaker benefits

We cover speaker travel and hotel and give you a free ticket. Because preparing a talk is hard work and we want value your time, we also provide a small monetary fee to compensate you for your time. Last year it was $200 for every speaker. We expect it to be more this year. If this is a problem due to travel issues (it can sometimes be harder to travel internationally if you are being paid for work you will do while traveling), let us know and we can work something else out.

We will have a speaker dinner where you get to associate with some of the brightest people in the community and commiserate about how stressed out you are for your talks, a fun speaker gift, the chance to walk out on stage to the intro music of your choice (just like Gob), and the everlasting fame and glory that accompanies speaking at a conference. Speaking is hard work, but we also work hard to make it worth your while.

If you buy a ticket and are accepted to speak, we will refund you the price of your ticket.

Some talk ideas

No idea what to talk about? Here are some ideas that could be interesting (but we are in no way limiting suggestions to this list of ideas).

  • Observables and React
  • Rendering to non-DOM targets (A React-to-Minecraft renderer? Why not?)
  • Managing asynchronous Flux/Redux state
  • What React can learn from other frameworks
  • Pitfalls in building reusable React components
  • The ideas of React throughout the history of computing
  • React and art
  • Server-rendered React using AWS Lambda
  • Teaching React to beginners
  • Learning React as a junior developer
  • Understanding React internals to contribute open source

Let us help

Do you have an idea that you aren't sure is ready for submission? Are you concerned you don't have enough experience to speak? Do you have questions about anything regarding the CFP? Email us at and we will be happy to discuss talk ideas or anything else related to the CFP process.

Code of Conduct

All attendees, speakers, sponsors and volunteers at our conference are required to agree with the following code of conduct. organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensuring a safe environment for everybody.

Need Help?

Email us at

The Quick Version

Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, or religion (or lack thereof). We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.

The Less Quick Version

Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.

Participants asked to stop any harassing behavior are expected to comply immediately.

Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualised images, activities, or other material. Booth staff (including volunteers) should not use sexualised clothing/uniforms/costumes, or otherwise create a sexualised environment.

If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.

If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. Conference staff can be identified as they'll be wearing branded t-shirts.

Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.

We expect participants to follow these rules at conference and workshop venues and conference-related social events.

This Code of Conduct is borrowed from Conference Code of Conduct.