conf.io

download done
downloading data for offline use
talk details
reviewing talks using a deck swiper for best UX
scoring talk
list of existing sessions
speaker details
deleting session
session detail, mainly about the meetup or conference
first login
list of reviewed talks, ready to sync
sync finished
syncing actions, votes that were done offline with conf.io server
empty actions list
home screen
conf.io schedule
scanning QR to login
login to an existing session
conf.io cfp home page
conf.io cfp login with mobile app

Inspiration

Conference & meetup organizers usually have a hard time when it comes to tooling, having a platform that does it all started to feel like a dream, conf.io comes to solve exactly that, using nothing but open source software.

What it does

conf.io is a platform that allows conference or meetup organizers better manage their events,

starting from the CFP application, that manages the complete workflow from submitting a talk, voting, accepting and publishing the schedule.
the schedule web app that came to solve one of the legacy CFP schedule's UI/UX problems.
the reviewer app which is an offline first mobile application that allows conference or meetup organizers review the proposals offline, then sync them with the CFP later on.
integrable with alf.io for the best check-in experience.

How we built it

conf.io reviewer is an open source mobile application that was built using React Native, taking from and back to the community, the repository can be found here: https://github.com/x-hub/confIO.reviewer.
we are mostly using a fork from https://github.com/nicmarti/cfp-devoxx which can be found here: https://github.com/x-hub/confIO.cfp, we had to do a major UI improvement & added few screens such as the one that allows the user to scan the QR code & also few APIs that allows the API consumer to get the event details.
we also worked on a messenger bot that will help the attendees get the most out of the event, which is also opensource and the repository can be found here: https://github.com/x-hub/confIO.messenger.

Challenges we ran into

we know the quantity of data we'll be dealing with and that's why we architectured our application in a way that is optimized for data read & write.
using Lottie animations got our application to run a little slow, but that's a tradeoff that we are ready to pay when it comes to UI/UX.
handling our application state became tricky as the code grows
messenger API Manual isn't good at all!

Accomplishments that we're proud of

we're proud of the UI/UX, minimal and elegant.
we're proud of the app's performance.

What we learned

optimization isn't easy & makes your code look ugly.
thinking on a solid architecture that allows us to scale, and that there is always a better architecture.