Week 3: Refining User Sign-in, About Page, & Multiple Riders
Welcome back readers,
During the 3rd week of our project, our team focused on refining the user sign-in screen, creating an about page, and adding in the multiple rider functionalities.
Kevin and Tyler worked together to improve the Google Sign-in that they completed last week. The next step for our Sign-in/Home screen was to add the Augustana logo and improve the overall layout and feel of it. We made the page more appealing to our users with a header for ACES and a colorful Augustana logo.
The next step was to restrict the sign-in to only @augustana.edu email addresses. By restricting the sign-in to only Augustana emails, we are able to ensure that only Augustana student are allowed to request ACES services. The implementation of this restriction was simple! All we had to add to the code was a second part to the conditional statement when the user tries to sign in. Basically, we just had to check if the email contained "augustana.edu." We decided that if it does not contain Augustana's email address, we would display an error and sign the user out immediately.
Tyler and Kevin also implemented the Sign-out button on our maps page. Now, when a user clicks the back button in the lower navigation bar, the user will be signed out and taken back to the homepage.
We also decided to add an About Page to the Sign-in/Home screen of our app. This about page has a description of what the ACES service does, the hours for ACES, and contains the phone number to call to reach the dispatcher at ACES.
Also, I think that it is important to mention how we are going to be handling adding multiple people to a ride. During the first week, we realized that ACES currently allows students to call in and request pickups for more than just one person. After talking to the ACES representative, we decided that the easiest way to add this capability into our app would just be to allow the user to specify how many students are being picked up for the ride they are requesting. This way we won't have to handle the names and emails of everyone in the ride. To do this, we are either going to add an incremental button at the bottom of the map page or possibly create a new activity after clicking submit to ask how many riders. We will make sure that the number is realistic (1 or more). The information about how many riders will be in this request will be sent to ACES along with the other data.
We only have one more week before the end of our first sprint! In this upcoming week, we hope to have the predetermined location choices for students to choose from, the communication between the ACES and our app, and a pseudo estimated time of arrival. With these elements completed, along with the components that we have already developed, we should have a basic, working ACES app.
Be sure to tune in next week to see our how our app is doing after the first sprint!
Thanks for checking in!
Team Aardvark
During the 3rd week of our project, our team focused on refining the user sign-in screen, creating an about page, and adding in the multiple rider functionalities.
Kevin and Tyler worked together to improve the Google Sign-in that they completed last week. The next step for our Sign-in/Home screen was to add the Augustana logo and improve the overall layout and feel of it. We made the page more appealing to our users with a header for ACES and a colorful Augustana logo.
The next step was to restrict the sign-in to only @augustana.edu email addresses. By restricting the sign-in to only Augustana emails, we are able to ensure that only Augustana student are allowed to request ACES services. The implementation of this restriction was simple! All we had to add to the code was a second part to the conditional statement when the user tries to sign in. Basically, we just had to check if the email contained "augustana.edu." We decided that if it does not contain Augustana's email address, we would display an error and sign the user out immediately.
Tyler and Kevin also implemented the Sign-out button on our maps page. Now, when a user clicks the back button in the lower navigation bar, the user will be signed out and taken back to the homepage.
We also decided to add an About Page to the Sign-in/Home screen of our app. This about page has a description of what the ACES service does, the hours for ACES, and contains the phone number to call to reach the dispatcher at ACES.
Also, I think that it is important to mention how we are going to be handling adding multiple people to a ride. During the first week, we realized that ACES currently allows students to call in and request pickups for more than just one person. After talking to the ACES representative, we decided that the easiest way to add this capability into our app would just be to allow the user to specify how many students are being picked up for the ride they are requesting. This way we won't have to handle the names and emails of everyone in the ride. To do this, we are either going to add an incremental button at the bottom of the map page or possibly create a new activity after clicking submit to ask how many riders. We will make sure that the number is realistic (1 or more). The information about how many riders will be in this request will be sent to ACES along with the other data.
We only have one more week before the end of our first sprint! In this upcoming week, we hope to have the predetermined location choices for students to choose from, the communication between the ACES and our app, and a pseudo estimated time of arrival. With these elements completed, along with the components that we have already developed, we should have a basic, working ACES app.
Be sure to tune in next week to see our how our app is doing after the first sprint!
Thanks for checking in!
Team Aardvark
Comments
Post a Comment