Too often, when we travel, we have no efficient way of sharing photos with our travel-buddies. Too often, we lean over awkwardly on the ride home and say, "eh, send the photo on telegram leh". And our friends oblige, only to be asked again: "Eh, send me also leh." What's more, for all that trouble, our precious photo memories are before long lost in a bloated, hardly-organized camera roll, leaving us furiously swiping at our screens whenever we want to reminisce the good times we had on our past travels.
What it does
Trippy is a one-stop solution for the sharing, syncing and storing of media memories. It allows users to create and join virtual "journeys", which in turn enables them to upload their photos into a Journey Repository in the cloud, which is used for automatic synchronization across Journey-Buddies by Trippy.
How I built it
We used a hybrid approach to our back-end, utilizing Amazon Web Service's cloud storage solutions for media entities, while maintaining other states/data on a lightweight SQLite database. We configured our APIs using the elegant and extensible (Python) Flask library, and built our front-end using React Native.
Challenges I ran into
Integration was definitely a challenge, as we ran into several unforeseen obstacles, from network security restrictions to incompatibility issues between devices. Otherwise, we found keeping awake mighty difficult.
Accomplishments that I'm proud of
We developed a really beautiful UI on the front-end, which surprised even ourselves! We also configured a fully-functioning back-end with various API endpoints.
What I learned
Gradual integration with a walking skeleton is probably better than big-bang integration at the end.
What's next for TrippyApp
We'll be fleshing our the rest of our functionalities, and will spend loads of time working on our UI/UX. We're also looking at deployment solutions for our back-end + APIs, and hope very much to release our app on the AppStore/PlayStore sometime soon!