In light of the COVID-19 pandemic, our team has been wanting to travel overseas to explore the world. However, this comes with its own set of challenges. Ever so often, group travelers pay for shared expenses, only to find out that everyone has the same big notes given to them by their moneychangers. This makes the process of logging transactions and paying back one another an extremely troublesome one.
What it does
This is where SplitLux comes into play. Splitlux expedites the process by splitting and monitoring bills in an efficient manner. This minimizes the potential for disputes and ambiguity while maximizing the efficiency of payment and recollection of debts. Users can create travel groups to keep track of shared expenses, as well as the amount contributed by individual groupmates. Group travelers can then easily take turns to pay for shared expenses without worrying about calculating the amount to pay one another. At the end of the trip, users can simply use SplitLux to calculate their trip expenditure and find out who to pay and how much.
How we built it
Splitlux adopts an architecture that is split predominantly into backend and frontend. Our backend is based on Python using Django. Using Django, we used the REST framework to create the API endpoints in order for the frontend to query. Since a large majority of people use mobile phone applications wherever they go, our frontend will be based on Flutter, which supports both Android and iOS devices.
Challenges we ran into
This was the first time our team used and the unfamiliar syntax took a while for us to get used to. Moreover, linking up the frontend to the backend was also a challenging process that the team took a rather long time to figure out.
Accomplishments that we're proud of
Our team is proud of the fact that we managed to successfully complete a functional flutter application with no prior experience. Given that one of our group members had an internship prior to the hackathon, there was little time to learn the syntax of flutter and make the necessary preparations.
What we learned
Our most significant takeaway from this hackathon was learning to fetch data from the backend using a REST API. This was a concept that we did not have prior knowledge of and learning to do so has been extremely fulfilling.
What's next for Splitlux
Moving forward, we hope to extend the flexibility of SplitLux by providing users with the option to input variable expenditure amounts in a shared expense. For example, a shared expense of $20 can have 15$ attributed to User A and the remaining $5 attrributed to the rest of the group members.