hSenid's blog on Outsourcing

We have established what the different device platforms are, and so the next question is which version of the .NET Compact Framework should you choose to target? “The latest version” would seem to be the obvious answer, but, as with many things concerning devices, it’s not quite that simple! As the developer, you choose a version of the .NET Compact Framework on which to build your application. If you choose version 1.0, you can be reasonably confident that your application will run on all devices because versions 2.0 and later of the .NET Compact Framework runtime run applications that were built to run on an earlier version. However, if you write code that uses features only available in .NET Compact Framework 2.0, that version of the .NET Compact Framework runtime must be installed on your target device for your application to operate.

The versions of the .NET Compact Framework runtime that are supported by the different mobile platforms are illustrated in Figure 1-5. Note that the figure does not represent an accurate timeline for the release of the different mobile platforms (for example, Windows CE 5.0 was released earlier than the Windows Mobile 5 operating systems) but is purely intended to illustrate run-time support.

Figure 1-5: Supported platforms for different .NET Compact Framework versions

Microsoft does not manufacture mobile devices, but it does supply the software for such devices. As part of the license agreement, device manufacturers that manufacture devices that use Windows Mobile software must agree to preinstall the .NET Compact Framework runtime on all Windows Mobile-based smartphones and Pocket PCs. However, because it takes quite a long time to design and release a new device, the availability of the newest version of the runtime on devices in the marketplace lags behind the release of the software by Microsoft.

The hSenid Outsourcing division has been developed on the expertise that was gained fromdeveloping product based applications. Our domain expertise in the Telco Grade and Mobile arenas and our in depth knowledge in mobile switching (IN systems, SMSC, MMSC, USSD, etc) has enabled us to provide total Outsourcing services including product development life cycle services to both mid to large sized companies worldwide.

Our team of expert engineers with vast experience and expertise of the industry that is capable of delivering custom Mobile Handset applications on Apple iPhone, Blackberry, Windows Mobile, J2ME and Android and Symbian that ensures seamless and  unparalleled connectivity for your businesses and helps you stay connected and entertained always. We design, implement, and integrate handheld applications of any complexity ranging from advanced user interfaces to complicated networking applications such as sending emails, organizer, phone, SMS and more, to be integrated in one single handy gadget.

iPhone development capabilities

hSenid IM on iPhones consists of all traditional features and interoperates with every major IM service, including AIM, Yahoo, Google Talk, ICQ and MSN Messenger. In addition to vocal IM, it offers traditional text messaging to and from users of those services. iPhone users can chat with multiple friends across this service and also lets its users send each other pictures
whilst allowing users to login to any of the services simultaneously if desired.

Blackberry development capabilities

Cosco is an expense tracker that enables BlackBerry users to capture, categorize and report their expenses instantly allowing them to save time and money. BlackBerry users can enter up-to-date expenditure information on projects/trips and activities in an easy-to-use and straight forward manner since Cosco enhances the efficiency of Blackberry.

Windows Mobile development capabilities

With the launch of mStockTrading on Windows Mobile handsets, hSenid has been able to take the traditional trading of stocks to new dimensions. mStockTrading on Windows Mobile handsets can carry out straight-through trading and obtain up-to-the-minute information on the stock market anytime and anywhere.

J2ME Application development capabilities

mChoice Banking via J2ME is a next generation choice in banking for today’s busy lifestyles which provides enhanced data security with end- to- end encryption from phone to banking server. It allows banks to open personal branches in every customer’s mobile handset and enables bank customers to conveniently carryout secure banking transact ions ranging from regular fund transfers, utility bill payments to mobile topups via SMS, WAP or J2ME.

If you have to choose between a device running Windows Mobile and a similar device running Windows CE, the other factor you must consider is the availability of application programming interfaces (APIs) on each platform. The most obvious difference is that on Windows Mobile 5.0 and later you have access to additional managed code libraries that are not available on Windows CE; these libraries make it easier to interact with the platform. For example, the Microsoft.WindowsMobile.Status namespace contains classes you use to query system status for many different items, such as the current active network connection and Internet Protocol (IP) address, battery power, screen orientation, phone status, media player information, or whether the device is cradled. You can also register to receive notifications when a system status changes. Also, you can use classes in the Microsoft.WindowsMobile. PocketOutlook namespace to query and set Microsoft Office Outlook Mobile data on tasks, appointments, and e-mail. You can use other libraries to access hardware on the device such as the phone, a Global Positioning System (GPS) receiver, or a camera.

Of course, whenever possible managed code developers call APIs only in managed libraries, but sooner or later, every managed code application developer has to resort to Platform Invocation Services (PInvoke) calls to native APIs to access functions that are available on the platform but not through managed APIs. Having a broad understanding of features available in native APIs on Windows Mobile that are missing from Windows CE can help you choose between platforms. To access a native API, you must use PInvoke to call functions in native APIs that effectively do all the hard PInvoke work for you.

There are too many differences in native APIs to describe them all here. To get an understanding of which native APIs are available on Windows Mobile that are not in the underlying Windows CE platform, study the documentation that comes with the Windows Mobile SDKs.