To make work orders and parks services workflow easier for everyone in the City of San Jose
What it does
Our mobile application allows both residents and city staff members to report, view, and edit hazards/maintenance request tickets in parks immediately when the see them. They will also be able to view all tickets submitted and subscribe to them. Staff members/contractors will be notified when a ticket pertaining to their park district is assigned.
How we built it
Backend: MongoDB, mlab, Node, Express, Heroku Frontend: React Native
Challenges we ran into
Sorting through the mess of current infrastructure for submitting and sorting work orders in San Jose parks
Designing a scalable database: designing schemas that are inexpensive to scale when number of users grow, using indexing strategies to optimize lookup latency
Working cross-platform with MacOS and Windows machines
Accomplishments that we're proud of
We built the application prototype, a MVP (React Native frontend), and also were able to design and construct schemas for easier implementability of future features and scalability of the application.
What we learned
We learned to work with each other, put checks and balances on ideas but also respect them. We should have been more proactive in asking for help from our mentors.
What's next for Park Issues
Subscriptions based on properties of the ticket (category, priority, location, park name)
Integrate posts on Facebook, Nextdoor, and other social media as reports/tickets
Parks Admin dashboard:
Scheduling system for work-performing staff members
Prioritization and categorization for tickets
Machine learning for ticket assignment and prioritization