-
Notifications
You must be signed in to change notification settings - Fork 0
Team minutes Mobile
Each person create one interface specification for the area you are working on
- Nick, Jian, Terak: Get emulator running and display draft home page
- Cody & Sean: Make git directory structure in team fork
- Cody & Sean: clone the repository into a fresh directory and ensure can still display the home page
- Display home page on a mobile device
- Make an active button on home page that goes to another page
- take a username on the home page form
- Determine how the mobile app can 'call' the main app
- May want to think about whether the app should be allowed to go off line.
I did some more thinking about the mobile team's charter. As we discussed, we don't want to duplicate effort on the 'main' system, and we want the mobile app to have as close to the 'same' functionality as the main system as it can. So we want to make use of the main system's use cases and implementation as much as we can, but make the mobile UI act like we expect a mobile device to act.
Part of making the mobile app useful is to create some functionality unique to the mobile device. Though we didn't talk about this in the meeting, I wonder if the mobile team could brainstorm and create use cases related to some characteristic unique to the mobile platform, probably, but not necessarily, having to do with device location or data gathered from some other sensor on the mobile device, like the camera. (Maybe scan a mobile 'square' code and search for the company that made it.)
- Make a list of mobile platforms we will support. -- DONE: Gingerbread
- Create at least one use case for the stock market app that uses a unique feature of a mobile device. -- DONE
- Create a draft home page for the mobile device. Displaying "Hello SOUSMS" is fine. -- DONE: on the simulator
We'll talk about how to do the following on Wednesday:
- Create a GitHub fork for the Mobile team -- DONE
- All team members create a local repository from the Mobile fork -- DONE