Part 1 of the series shows how the Wireframe reminded me to prepare various codes (bearing calculation between two locations, getting travelling direction from GPS, etc.).
In this second part, I only care about the design assets that will be used. Composites will help me on 2 fronts:
- The Demo Scenario: sometimes you want to show how cool your app is, but can’t wait until it’s code-complete. Stitching design assets properly and hardcoding stuff (eg. when I pick a city only Jakarta is available, and all prayer time calculation & Qibla direction calculation will be based from Jakarta only) allow me to demo my app without waiting for it to be finished first.
For demo-ers, this can be used as cheat-mode like those Flash presentations where every where you click, the Success Scenario always happens :)
On a more technical viewpoint, the UX or the View, should not know anything about the Model & Controller anyway…the View should always display whatever data is supplied to it :)
- Researching more on code feasibility. For example, is it possible to set Opacity to the Application Bar so that the background image shows fluidly?
Lo and behold, here are the color composites for we.Muslim Windows Phone 7 app:
Splash Screen
Different background images for Fajr, Dhuhur, Ashar, Magrib, and Isha
Home Screen (Prayer Time)
Qibla Direction Screen
Well after looking at the composites, I know how many Image Controls I will need (you see, from the Composites only I realize that my app looks better with a custom “we.Muslim” logo instead of the usual text with Segoe WP font).
Well after this it’s time for code, code, and code! Stay tune for the next instalment of the Dissecting WP7 app series.