WHY ?? THIS APP….

- An app to reduce the burden from the conductors.

- To increase the use of digital currency.
- Bus journey and payment will be more systematic.
- Change the dependence on ‘change’.
- Reduce the wastage of paper by printing online tickets.
APP IDEA
• The basic idea behind our app is to book bus tickets directly via this
app instead of relying or bothering bus conductors.
• People can make their accounts linked with some payment method.
• Whenever they have to ride in any public bus they will have to enter
their source and destination and then make the transaction.
• Account details and profile of the passenger will be sent to the
conductor side.
• Ticket details will be sent to the passenger.
SECTIONS OF ‘बस-PAY’
Our app will be having three parts :
1. Server Side
a) Maintains the profiles of clients and conductors.
b) Sends notifications to the client (ticket details) and conductor (client
details).
c) Sends the total number of tickets issued to the conductor.
d) Maintains the transaction record.
2. Conductor Side: Has two interfaces.
3. Passenger Side: Has four interfaces.
INTERFACES:
• LAYOUT- .xml file using android studio.
• ACTIVITIES- programming the function of each button defined in the
layout using java scripts.
Modules of the passenger side interfaces
• Interface 0: Login
• Interface 1:
1. Profile of the client
2. Source
3. Destination
4. Payable amount
5. Number of tickets
6. Total amount
7. Pay/confirm
NOTE: once all the above options are correctly filled and the pay/confirm
button is pressed, the app will direct you to the second interface.
… continued
• Interface 2:
1. Conductor ID (As per the ID cards of the conductors).
2. Modes of payment.
3. Proceed to pay.
Note: Once proceed to pay button is pressed, It will direct you to a
secure payment page (As of now, instead of actual money transactions
the server will maintain records through a dummy account).
• Interface 3:
1. Display of ticket.
Modules of the conductor side interfaces.
• Interface 0: Login
• Interface 1:
1. Conductor profile.
2. Notifications centre.
3. Details of the journey.
4. Total number of tickets issued.
Cost involved:
• Maintenance of the servers (for now, we will be using the free google
servers)
• For hosting the application on the Google play store : ₹1750
Work distribution
Neelabh Dev- Few layouts, Google firebase and Activity coding.
Pushkar Hiray- Few layouts, Google firebase and activity coding.
Mrinal Dutt- Conductor side layout.
Sheshachandra- Passenger side layout.
Time allotted and new things learned:
Each of us allotted a minimum of few days in learning different aspects
of android making.
We do not know exact amount of hours spend as it was distributed.
Each of us learned different things and taught each others the basics of
that particular part.
Pushkar – Front end and backend coding.
Neelabh- Learned how to make different layout and how to link and
code to the java file.
Mrinal and Shesh – Learned how to make different layouts and how to
give constraints.
WORK DONE SO FAR
1. all the xml files.
2. activity page of sign up and client has been done
3. trying learning google firebase.
difficulties / hurdles
1. problems in the layout.
a. contraints observed in the apk file arent following its expected design of the
android studio layout window.
2. google firebase connection issues
a. All the activities of our app had to be connected to Google firebase, which
we tried implementing using the firebase tool box in the android studio, but
we faced some connection issues.
b. Thats why a local server was implemented to communicate between the
client and conductor.
Future
• We were not able to complete our project mainly because of lack of
knowledge and time.
• We are planning to read about the problems we faced and try to
solve them during our summer break apart from our internship.
• We will try to finish our app during this vacation as it is a very good
idea.
All the files:
• https://drive.google.com/drive/folders/1OqlCirPsx-YNeJsxkOXyvBD
77ir9Mq04?usp=sharing
Thank You!