What we planned for this week
- Implement Customized TableView (Image)
- Test CoverFlow (Usability) in real iPhone
- Single view for selected item in TableView
- Load image and display image from CoreData on single view
- Research & Code Examples for UISegmentControl
- Create first screen with menu from plist
What we actually did
- Implement Customized TableView
We customized table view to display the ingredients in the Single View. Basically we have two labels with a small font size, different colors and a smaller row height. We haven't customized the table view for the search results yet. - Test CoverFlow
We tested the cover flow usability in the real iPhone. We will give it a go in our App and we'll see how it goes. Unexpected exceptions are expected... - Single View & UISegmentControl & Load image
We implemented these. We are hiding and displaying the different parts of the view dependent on what segment was chosen.
Loading the image from CoreData was easier than we thought. - Create first screen with menu from plist
It works like a charm. - Steps view
We started creating the steps view and are still working on this.
Who did what
- Trying troubleshoot the mac to access the internet again (Chris)
- Added more recipes (Mandy)
- Implemented copying of database instead of importing the XML all the time (Chris)
- Implemented start screen, navigation from plist (Mandy)
- Added search control to the RecipeSearchViewController (Beat)
- SingleView with UISegment Control (Beat)
- Research customized TableView for search screen to show image, heading, subheading etc (Mandy)
Plans for the following week
- Customized table view for search results
- Finish steps screen
- Try to implement CoverFlow on steps screen
- Interactive search (smart search)
- Settings View
- Favourites View (Button on SingleView), think of storage of favourites (another entity or plist)
Overall progress
We are on track. After next week we will have implemented all our desired screens. What is missing are details in respect of the design of the views. Before being able to ship our app to the app store more things are in the queue that need further thinking and investigation.
- How to present the user the possibility to change the units (despite of changing it in the settings)
- How to get more recipes into our database
- Necessity of searching recipes online
- Necessity of an advanced search (e.g. exclude ingredients)
- Usability of the App - is the target audience satisfied?
Re-evaluation of risks
| Risk | Likelihood | Impact | Time lost | Action |
| Emotional outburst because of slow Unitec internet | H | H | Immense | Unfortunately we can't change it. :( Where can we complain? |
| Hackintosh problems, small screens and high possibility of crashing | H | H | 3 hour / week | Buy a real Mac. Problem: no money. Solution: Unitec pays. |
Comments