Archive for category Mobile Development
Back in the nineties, I did some development on the old Palm Pilot devices and later tinkered with some Windows CE development as well as .Net development on Windows Mobile 5.x devices, but the experience always left me feeling a little underwhelmed. However the recent popularity of touch screen based mobile devices such as the iPhone, iPad, various Android based devices, and now the new Windows Phone 7 launch has inspired me to investigate mobile software development again.
In that pursuit, I decided to attend the local Microsoft Presents — Windows Phone 7 Unleashed event put on by the South Colorado .NET User Group in Colorado Springs. The event turned out to be a good time and provided some good hands on labs to experience what development on a Windows Phone 7 device entails. Let me just say that nearly two years ago I had heard that bringing Silverlight development to the mobile market was in the works at Microsoft and the potential prospects that could provide was a factor in my decision to invest time in learning Silverlight on the desktop. Microsoft has done a good job of ensuring those skills transfer to the mobile development experience on Windows Phone 7. I was amazed at how easily a colleague and I were able to put together a Silverlight and WCF Service enabled Windows Phone 7 application during our hands-on labs.
Given my positive experience with Windows Phone 7 mobile application development, I began wondering how I might tailor the design and architecture of the web applications I’m building today to be ready for mobile integration in the near future. The web applications I build today are generally done as ASP.Net and/or Silverlight clients and frequently make use of AJAX and/or Web Services to access server-side systems and data. Additionally, I’ve been making a strong push to leverage jQuery in my solutions so being able to work with jQuery’s AJAX services would be a huge plus.
For the purpose of this discussion, let me start by defining two general categories of web services, each targeted at solving different problems. The first are what I’d call private application services, where the client-side and server-side components of the system are generally controlled by the same developing party. Their interfaces and features are often purpose-specific and aren’t necessarily intended for general public consumption. These types of services are well suited to JSON and AJAX implementations.
The second type of service category could be described as public services, where the service itself is the application and its purpose is to expose data and features to any number of clients both known and unknown. Often these are implemented as RESTful services because of their discoverable nature and cross-platform compatibility. It’s the first category of services that I plan to discuss today.
Private application services generally fall into two groups that differ primarily in intended consumption scope – local or application wide. For those who follow the MVC or MVVM design patterns, local scope web services can be thought of as view-specific callbacks with very limited scope such as a specific page or component on a page. In standard ASP.Net web applications they are often implemented as a WebMethod on an ASPX page or using traditional web services (.ASMX files). Application wide services, where the reuse of the service is unlikely to extend beyond multiple pages in an application or maybe a set of related applications, are often implemented as standard web services using ASMX files or using WCF.
A number of projects I’m currently working on have a need for both local and application wide services which can be called using jQuery’s AJAX features. I also have a desire to share the application wide services with Silverlight clients and want to leverage the binary XML serialization that was made available starting with Silverlight 3 when accessing WCF services. This requirement falls right in line with Windows Phone 7 requirements and would allow me to work with these same services when doing mobile development on that platform.
So to cut short what is turning out to be a fairly long blog post, I believe I’ve come up with a project configuration that meets all my requirements.
- I am able to easily make JSON formatted AJAX calls, using jQuery, to page-level Web Methods, traditional ASMX Web Service methods, and WCF service methods using the same client-side syntax. This will allow me to organize my services into functional groups and scope their reuse as appropriate (page, in-application, or cross-application).
- I’ve also figured out a way to configure WCF services so that they are simultaneously accessible as JSON based services for AJAX clients as well as binary XML based services for Silverlight and Windows Phone 7 clients. This simply requires specific web.config file settings.
Stay tuned for a follow-up post on this subject, where I will walk you through samples of this configuration using Visual Studio 2010, jQuery and the new templating plug-in, WCF, and Silverlight 4.
The need, or at least desire, for mobile enabled websites and applications has been steadily growing for quite some time. A number of my existing clients are now asking or planning for site upgrades that support mobile users and new clients often express a desire for these features as well. I suspect we are on the cusp of another technological shift similar to the 90’s era boom of web-innovation when so many client/server developers migrated to the web. Web-based application developers are no longer going to be able to ignore mobile development.
As a web application developer, I’m already familiar with HTML and CSS and have been experimenting with these technologies in the mobile space. HTML5 and CSS3 have some great features for making robust, rich internet based applications. I believe web-based applications targeted for mobile devices offer many advantages over native-app development, many of them the same as they hold over traditional desktop applications, but they currently have some limitations when it comes to accessing device hardware features such as the GPS or camera. Additionally, there are times when your application needs to be functional even if in a limited capacity when the user is offline; something that is very difficult to do with a mobile web application. For these things you need a native mobile application. However, as anyone who has looked into this knows, this requires a significant investment in time and money in order to cover all the bases.
Mobile application development for the .Net developer just got interesting!
Novell, a sponsor of the Mono project, has a couple of very interesting products in the works, MonoTouch and MonoDroid, which promise to allow .Net developers to build software for the iPhone, iPod Touch, iPad, and Android based mobile devices using C# and core .NET APIs. The iOS version is available now, while the Android version is in an early development phase. I’m particularly interested in MonoTouch’s ability to work with WCF services in a familiar manner, given that they are often a part of the web applications I build. This coupled with the ability to access the phone’s camera and GPS opens up a whole host of integration possibilities for a number of sites I’m working on; some of which are required to remain functional in an offline state. The Mono project has finally spawned something for which I can get excited about.
Read the rest of this entry »