jaorow / trippa

TRIPPA [Datadons-Carpooling]

Travel is expensive, both financially and environmentally. In New Zealand, solo driving is prevalent, resulting in numerous empty seats and a significant environmental impact. Approximately 73% of Kiwis choose to travel alone, collectively spending around 150 million hours on the road annually. As a result, transport emissions have become the fastest growing source of greenhouse gas emissions in the country, accounting for 20% of the total emissions produced.

At DataDons, we recognize the potential to mitigate these issues. While hitch-hiking has been a traditional solution, it lacks efficiency and safety. We aim to streamline this practice and shift the focus towards a more communal approach to travel, reducing both costs and environmental impact.

Introducing Tripa, a community-oriented carpooling app that aims to facilitate existing trips rather than creating new ones, promoting a safer and more sustainable travel culture in New Zealand. Please note that Tripa is distinct from ridesharing apps like Uber and Ola.

Getting Started

To set up and run the Datadons app and backend on your local machine, follow these steps:

1. Clone this repository.
2. Navigate to the datadons-app folder and execute npm install to install all necessary app dependencies.
3. Run npm start to launch the app.

Backend

backend is currently hosted on azure however at azure link if local host is requred follow these steps

5. In a separate terminal, navigate to the datadons-backend folder.
6. Execute dotnet run to initiate the backend.
7. change the endpoint const within ApiHandler.js in datadons-app/src/services

Features

The Datadons application facilitates the following:

• User Management: Authenticate and authorise users.
• Data Handling: Manage and store user and trip data efficiently.
• API Integration: Robust endpoints for fetching, updating, and manipulating data.
• Trip Management: Users can view a list of available trips, and if registered as a driver, can add new trips.
• Communication: A live messaging system enabling seamless communication between users.
• Search: Integrated searching functionality, allowing users to find the most suitable trip based on the location criteria.

Technologies Used

• Frontend: React Native-EXPO
• Backend: .NET Core [0.7]
• Deployment: Azure App Service

Project Mangament

Github Project page

Github Project page

Folder Structure

Frontend

Within the src directory "datadons-app", the organisation is as follows:

• AccountScreen.js: React Native component for the account screen.
• AddTripScreen.js: React Native component for adding a trip.
• App.js: Main entry point for our React Native application.
• HomeScreen.js: React Native component for the home screen.
• MessageScreen.js: React Native component for the message screen.
• NavigationService.js: Service for managing navigation within the app.
• app.json: Configuration file for our React Native app.
• assets Folder containing various static assets used in our application, such as images, icons, and videos.
• auth.js: File handling authentication logic for our app.
• babel.config.js: Babel configuration file for our project.
• components: Folder containing reusable React Native components used across different screens of our app.
  • NextButton.js: A component for the 'Next' button.
  • Onboarding.js: Component for the onboarding screen.
  • OnboardingItem.js: Component for each item in the onboarding screen.
  • Paginator.js: Component for the paginator.
  • slides.js: Component for managing slides within our app.
• package-lock.json: Automatically generated file based on the exact versions of our installed npm packages.
• package.json: File containing metadata about our project and the list of dependencies.
• services: Folder containing files related to various services used in our app.
  • ApiHandler.js: File for handling API requests and responses.

Backend

Within the src directory "datadons-backend", the organisation is as follows:

• controllers: Handles API calls and HTTP request management.
• models: Structures for database interaction.
• data: Utility functions (idk what to write here tbh ).
• dtos: Functions assisting in data manipulation and shaping, as needed.

Future Plans

• Enhanced Booking System: In the next iterations, we aim to revamp the booking system. Instead of instant bookings, users will request to join a ride and drivers will have the authority to accept or decline these requests, offering more control and flexibility to the ride providers.
• Payment Integration: We are looking forward to integrating Stripe as our primary payment gateway, ensuring a secure and seamless transaction experience for our users.
• License Verification: To enhance the safety and authenticity of our platform, plans are in place to introduce a license plate verification feature. This will be accomplished using the CarJam API, ensuring only genuine drivers are part of our community.