Signin
DUE Wed, 03/13, 2 pm
This assignment may be completed individually or in team of at most 2. You can partner differently for each lab.
In this lab, we add Google Sign-In, with biometric authentication, to Chatter built using declarative UI. We also develop the code using coroutines instead of relying solely on callbacks. There are three TODOs in this lab, to give you a chance to work with side-effect in UI with uni-directional flow and calling asynchronous functions. Assuming you’re fairly comfortable with mobile programming by now, the whole lab could take about 4 to 4.5 hours to complete.
Assignment specs
There are TWO pieces to this assignment: the front end and the back end.
The suggested work flow is to work on the front end until you can obtain the ID Token issued by Google Sign-in, then switch to work on the back end, and then return to finish up the front end:
Unlike the Audio lab, the back end of this one is rather more substantive, but it’s still mostly just a tutorial for you to follow and cut-and-paste:
If you choose to work on the back end first, be prepared that you won’t be able to test it until you’re part way through your front end. Once you have built and tested both your front end and back end, you MUST get your front end talking to your back end.
Objectives
- Further explore working with side-effects in UI with uni-directional flow
- Learn coroutines and suspending/asynchronous functions
- Learn structured concurrency
- Learn how to show an alert box in SwiftUI
- Learn how to work with an OAuth2.0 API (Google Sign-in)
- Learn simple persistent storage of user variables
- Learn biometric-guarded key-value store
- Learn how to add a new API (
adduser) to the back end - Learn back-end token checking and additional RDBMS work
| Prepared for EECS 441 by Sugih Jamin | Last updated: February 21st, 2024 |