OK, it is time to create that first app for Windows phone. Then porting it into Windows 8 is the next step. Will it be too much difficult? No, not at all!

Let’s start by creating a Windows Phone app that synchronizes with Google Chrome environment.  To sync Windows Phone for accessing the Chrome bookmarks, recent viewed pages, passwords, and also open tabs for the phone. The entire procedure is carried out through the help of Chrome SYNC Protocol. This protocol is taken directly to Google’s servers. The approach is very similar to Chrome’s approach for the purpose. Let’s share some tips:

The apps can be created very effectively by simply downloading CHROMIUM SOURCE CODE. Then, developing the windows phone app and finally porting it into the Windows app store becomes easier. In fact, running the app on Chrome browsers in a PC becomes simpler. Taking help of languages like C# is necessary to develop the app. And be rest assured to face with positive reviews once the application is released.

Next step is to release one similar application for iPad and iPhone, while porting the app using MONO TOUCH to iOS. It is easier and much more convincing to port an Windows phone apps to Windows app Store using MONO TOUCH. Before going any further, let’s share some basic information about MONO TOUCH.

MONO TOUCH provides C# bindings to those native iOS frameworks. However, it never provides any UI compatibility layer for running Silverlight on the iOS. However, this doesn’t restrict designing the UI using NIB files, creating OUTLETS, ViewControllers etc. You use MonoTouch to create a native app, that is indistinguishable from an app coded in Objective C. But the point is, will it be possible to port the UI? Remember, UI porting is quite straight forward. Simply put an authentic iOS UI on it for porting the backend code. All the backend stuffs include syncing, authenticating, storing in the database, etc.

Porting the code is pretty simpler than one can even think of. When Windows Phone apps started to get created for the first time, the basic idea was not to port it to iOS or Windows 8. However, using the MVVM (standard) pattern helps in decoupling the database code and sync logic from UI code.

Using more than one solution (developed in Visual Studio) helps much in the cause. But, iOS solution usually references same Source Control folders as Windows Phone solution even for shared classes.

Database access is a major factor while porting of apps into Windows Store is concerned. Those phones featuring Windows 8 Operating System features direct support for SQLite. And using SQLite on the Windows Phone allows the database coding structure to remain unchanged.

The best way to run the application after development is through iOS simulator. It is absolutely a simple procedure and helps in easy communicating to Google’s servers while dumping out all the synchronized bookmarks.

It is easy enough to port Windows Phone App to Windows 8 if the above guidelines are followed properly. There are other ways too; but, why complicate the scenario, when end results will be the same!

Author Bio: This post is written by Brianne. She is blogger by profession. These days she is working with Bill Gates in an online promotion.

Tags: APP, chromium, ios, ipad, iphone, mono, monotouch, phone apps, port window, port windows phone app to windows 8, windows 8, windows phone, windows phone app, windows store, windows store app