If you’re interested in tech and/or you’re a developer, you’re arrived at the right place. At BuckleUp knowledge sharing is a huge part of our work ethic and company philosophy. So we want to share some of what goes on behind the scenes and under the hood of BuckleUp. Get familiar with the technology that powers the connection of Digital Nomads.
Our innovative use of mesh network technology combines Wifi hotspot, Wifi Direct, MTU Protocols, Bluetooth, Bluetooth Low Energy components such as GATT Profile, ATT Protocols and P2P to achieve Cross Platform functionality that is stable, reliable, fast and secure. With the help of our AI the application chooses the best way to connect people using OS and Hardware compatibility.
All the features are automatically enabled or disabled, based on AI functionality and depending on the needs of the system. Our peer-to-peer networking allows people to connect and exchange messages in real-time regardless of network connectivity. The application synchronises offline/online and ensures that every message is delivered.
Because security is important, our protection meets banking standards, using strong encryption and certificate checks, tamper detection and arithmetic obfuscation for providing a secure and safe, reliable environment for our users.
Additionally, data is stored in a MongoDB database hosted on an AWS instance, like the application servers. Every request accessing data is required to use an access token using JWT encryption that is refreshed on login, to make sure that only registered users have access to data. This access token is also linked to the ID of the user using it, allowing to stop users from writing on other users’ data.
To add a trip, users can either specify the flight code (carrier name + flight number) and the date of their flight, or scan a barcode, which will give the same data to the server. The server then calls a separate API, Flightstats, to get all the necessary data, and stores it in Mongo.
Every 12 hours, flight data is refreshed, and if, at refresh, a flight departure time is less than 2 days after the current time, a request is made to fetch the updated data for it, with additional airport info (the departure and arrival gate) and new matches that have added the same trip in the meantime. Once the trip is done, it is stored in the user’s past trips, and is not refreshed anymore.
Protection for location again last location is handled by google and radar will all possible restrictions that mean your location is not exact.
Just like personal data, locations are stored in a MongoDB database, in a separate collection than the rest of the data. Locations are fetched using the devices’ GPS data on a regular basis when the user is logged. Every request accessing the location also requires a JWT token that restricts access to it. Every location is stored with a timestamp and older locations are regularly removed from the database.
BuckleUp to Learn about and Discuss our Tech
Meet the Devs