- This objective may include but is not limited to: choose which sensors are appropriate for your application; design location awareness (when to use different levels of GeopositionAccuracy); location awareness system setting
MSDN, Location for Windows Phone: http://msdn.microsoft.com/en-us/library/ff431803(v=VS.92).aspx
- This objective may include but is not limited to: manipulation events (ManipulationStarted, ManipulationCompleted, ManipulationDelta)
MSDN, Launchers and Choosers for Windows Phone: http://msdn.microsoft.com/en-us/library/ff769556(v=VS.92).aspx
MSDN, Gesture Support for Windows Phone: http://msdn.microsoft.com/en-us/library/ff967546(v=VS.92).aspx
- This objective may include but is not limited to: pass parameters (NavigationContext API), manipulate the navigation stack (NavigationService API), use of the Back button, PhoneApplicationPage class and PhoneApplicationFrame class and the difference between these two classes
MSDN, Frame and Page Navigation for Windows Phone: http://msdn.microsoft.com/en-us/library/ff941091(v=VS.92).aspx
Links to source material:
GeopositionAccuracy has two settings (source):
Default – Optimize for power, performance, and other cost considerations.
High – Deliver the most accurate report possible. This includes using services that might charge money, or consuming higher levels of battery power or connection bandwidth.
Manipulation Events (source):
- ManipulationStarted – This event occurs when the user starts a direct manipulation by placing their finger or fingers on the screen.
- ManipulationDelta- This event occurs repeatedly while the user is moving their finger or fingers on the screen.
- ManipulationCompleted- This event occurs when the user removed their finger or fingers from the screen