Inspiration
- We went to a really awesome event here in San Francisco and grabbed some great photos of the event, but it didn't feel right just to post them on our social media accounts just for our friends to see. What if the people from the event can find themselves in one of thee photos we take and have an awesome photo of themselves which otherwise would have never been discovered? We created Clixz as a way to both connect event participants to more content from an event and allow other users to explore events in their area through photos, or what we like to call "clix."
What it does
- Anyone can upload clix to an event, and Clixz users can create new events for people to start sharing. Users can view and download the media from the event.
How we built it
- We have a deployed backend and an AWS S3 bucket to store the media data. Our frontend, hosted on vercel, talks to that backend to retrieve data and render the content based on what's stored in our database. The website is a react-app with various routes to handle specific user events and features like viewing event media or creating an event.
Challenges we ran into
- Some of the challenges we ran into was having all the functionality required to store and facilitate user and content data between our website and server. There were a lot of small nuances we hadn't fully considered but definitely needed to ensure proper security, functionality, and user experience while interacting with Clixz.
Accomplishments that we're proud of
- Having a product other people can contribute to with their photos from the DonsHack.
- Great git practices, (44 Pull Requests successfully merged)
- Mobile Accessible
What we learned
- How to be more mindful of security risks and how best to defend against them, especially with a product that accepts user generated content.
What's next for Clixz
- More advanced security measures such as content moderation and advanced sanitization
Log in or sign up for Devpost to join the conversation.