Home > SSW Standards > Rules To Better Interfaces - Mobiles
I've been putting together Development Guidelines for my employer and in the process have reviewed many published standards (in the .Net arena) from around the world. In each category, the suggestions at SSW are always among the best.
Leon Bambrick -
Do you agree with them all? Are we missing some?
Let us know what you think.
-
Do you know when to build an iPhone app over an iPhone web app?
Depending on:
- Budget
- Usage of native API
- Existing web app and just add CSS
Note: An iPhone (or WP7) web app without a network connection, will not load the
web page you were on previously.
-
Do you know when to build a WP7 app over an iPhone app?
-
If your app is build on Silverlight today.
-
Reasons are:
- Time to market
- Lower cost
- Reuse MVVM
- Reuse Silverlight controls
- Reuse the Business and Data layer
-
The Biggest thing going for windows phone is:
- .NET dev shops
- Environment more productive than xcode
Note: WP7 is built on Silverlight 3 (not Silverlight 4)
Note: WP7 was built by a 'web team' not "Rich client app team', so some issues exist:
- Bing map control relies on host page (authentication)
- Avoid using System.Windows.Browser.dll in your Silverlight App (as it works only
OOB on desktop) and you will have to use a different control on Windows Phone 7
-
Others reasons are:
- You can deploy your app without going through the appstore/market place. E.g. my
SSW business app
|
Appstore:
|
No
|
|
Market place:
|
Yes
|
-
Turn around through the appstore is quicker:
|
Appstore:
|
1-3 weeks
|
|
Market place:
|
2 days (Quicker since it is managed code. Unmanaged code is easy to spot)
|
-
App store is blocking applications MS wont
Related Rules
Read the specific rules below:
Links
Acknowledgements
Adam Cogan