Week 6: Refining User Requirements

Hello readers,

This week we made some changes to our dispatch app and our user app.  In the rider app, we changed the number of riders entry from an editable text field to a drop-down list.  We felt this was a better option as there is a limited number of choices that the user should be able to choose from--a minimum of one and a maximum of seven. This also eliminates room for error in choosing the number of riders, as they will not be able to input values outside of the range.  Here is a screenshot of the change:






























Another thing we finished was the ON/OFF switch controlled from the dispatcher app. The dispatcher/driver can simply click the button to turn the ACES service on or off. It turns red when off, and green when on. This sends a trigger to the firebase database, changing the flag value to either ON or OFF.





























When the user goes to the main login screen and tries to login while ACES is down, they will be greeted with the following screen. This allows the user to see the hours during which ACES will be active, for future reference.





























We still have a few things that we need to work out in our app.  We will be working on testing with actual devices so that we can fix any errors that might occur. We will also clean up some pieces of the user interface that still need work.

Thanks for reading! Check out our final version in our next blog post!

--Team Aardvark

Comments

Post a Comment

Popular posts from this blog

Week 5: Improving the Map and Dispatcher App

Image
Greeting readers, This week we worked on improving the map design and finishing the Dispatcher app functions. Megan and I mostly spent our time to work on the map to improve its functionalities and design. Firstly, we improved the design and the color of the map to make it looks more appealing and smooth. We also added the bounds for Augustana College area, so when the students choose the "out-of-bound" locations, the app will not let them to do so and notify them to choose the locations in bounds. If the students choose the "out-of-bound" location.. ..., the app will notify them. Furthermore, we added a button on a top right of the screen to recognize the Current Location of the rider. If it is in the Augustana College area, we will choose it as a Start Location, and find the actual address using the Latitude and Longtitude. If it is not in Augustana College area, we will notify the riders that they are not in the ACES service area. ...
Read more

Week 8 Completion and Future Plans

Image
Hello readers!! We have finally made it to the finish line of our ACES app.  Unfortunately, we are not able to continue perfecting our app for students on Augustana's campus.  In our last week we added an update time function to the dispatch app that allows the dispatcher to change the wait time if there was a mistake or a delay causing a major change in the wait.  We were also making sure our demonstration would run smoothly. We finished up this week with our presentation to the Computer Science department and it went well. Our apps worked without any issues.  We were able to finally show off all of our hard work from the last 7 weeks!!  If this project is to continue at a later time we had some suggestions on additions to the app.  1.  There should be a way to allow students to use the app without needing to allow location services(not all people are willing to give away their location) 2.  Indicate where the boundaries are at on the...
Read more

Week 4: Dispatcher App, Custom and More Accurate Addressing

Image
Welcome back readers, This week we worked to get the user app working in real time with a dispatcher app would use to speed up the processes of logging rides. Megan and Tan spent their time cleaning up the google maps page of the user app.  It is functional for rides that are requested with locations around campus with the auto complete feature.  They were also able to get the pins marked for the start and destination locations.(As displayed below)  Lastly we got all of the parameters finally on the display so the number of riders is now sent to the database. Once the ride is requested they are now sent to a page that displays how long it will take for their ride to come so for now we have a page that does not display a time.  Kevin and I created the layout for the dispatcher to allow them to view all the requested rides and to have the ability to add rides and remove the ride by clicking on them.  Once the ride has been requested it is sent to th...
Read more