We kicked things off with an intensive brainstorming session, where we chatted through all the ideas and came up with some initial concepts.
Our initial vision was pretty ambitious. We wanted to create a box that integrated all kinds of functions. We wanted to use GPS to record the location, BLE to detect which cell phones were currently boarding, and a light barrier to check the number of people boarding. We also planned to create three different user interfaces—one for the end user and two for the public transport companies that send fare evasion figures and help set up the system. The system should be able to be used on all public transport, not just buses.
That means trains, buses, planes and ships too.

This first idea included lots of different features and was meant to be a complete solution for the whole transportation industry. As the project went on, though, we realized that trying to implement all these features would not only take longer than we thought, but it would also get in the way of the core idea.
All these planned features made the project look more like a bunch of random functions than a focused idea. So we decided to go back to the drawing board and focus on the essentials. We trimmed the features down to just the essentials so we could zero in on the core idea: making bus travel easier and more convenient. The new plan was to have a box that works with just one app and is only for buses at first. This made things simpler and let us focus on one API, for example, without having to think about other interfaces.
This focus helped us make the core idea work well and get it off the ground, and create a solid MVP (Minimum Viable Product) that we could build on later.

Software Process

Next, we started working on the user interface and app features. First, we put together some wireframes and design dummies in Figma to get a feel for the user experience and make sure the app would be simple to use. The wireframes were really important for planning the user experience in advance and spotting any potential design issues early on. During this phase, we made sure the user experience was simple and straightforward. We used these wireframes to build the mobile app with React Native, which lets us use it on different platforms.

We chose React Native because it lets the app talk to the beacons via BLE.
We made sure to get the core functions up and running smoothly and efficiently, including things like automatic beacon detection, trip data collection, and background processes. The software development process was very iterative.
Once we had the first functional prototypes up and running, we did a few rounds of user testing to get feedback and make sure we were constantly improving the app and the features it had based on what the testers had to say. It was really important for us to get direct feedback on how easy the app was to use and what we could do to make it even better. One of the most important things we wanted to get right with the app was the setup process. We wanted it to be quick and easy for the user.
Once you've set up the app, it's basically ready to go. It runs in the background and takes care of all the steps needed to record bus journeys and organize billing. You can also monitor your journey and see which costs have already been debited.
This way, you're always in the know and in control.

Hardware Process

The hardware process was all about choosing the right technical components to make the beacon technology work. It was crucial that the beacons were energy efficient, cost-effective, and easily retrofittable in buses to make it easy to roll out across the entire fleet. After quickly thinking through what the hardware needed to do, we decided on an ESP32 LilyGO, which has both BLE and GPS capabilities, covering all of our functional requirements. To keep costs down and make it simple to retrofit, we designed a plastic housing and 3D printed it. We also added a strap with a buckle to the housing so it can be mounted on various poles.

This was a smaller step than the software development, but it was crucial to create the technical basis for the entire system and ensure smooth functionality in everyday use.