The Windows Mobile RSS (Reed and Steve Stuff) Feed : Ecosystem

Microsoft OneApp – what is that thing?

hegenderfer — Fri, 30 Oct 2009 15:15:56 GMT

Okay, so this is officially my second week in the OneApp team, and I must say I am really impressed with the group…sharp cookies one and all. I am definitely bringing down the bell curve here :)

But I am equally as jazzed around the opportunities that OneApp will bring to mobile developers world wide. The ability to reach MILLIONS of users with the EXACT SAME code base ACROSS DEVICES…that is cool!

Of course, the reason we can do this is because we have a CLR that runs above a VM on the device (and boy, it’s a tiny shim…very efficient). So, you won’t be ‘going native’ with OneApp to the metal (so to speak), but you can create some extremely cool apps.

Best of all, for you folks out there that like to tinker, the platform supports free apps and a free tool chain…when I say free, I mean free. As in really free. As in, no cost (aside from your valuable time, of course). I’ll have more info to share in the coming weeks and months, but it is very nice.

And the distribution model should be killer as well (remember the MILLIONS of users ACROSS DEVICES thing above…was that a gratuitous use of caps?).

We are still finalizing some pieces of the business models and such, so I can’t talk about those right now, but I will say that this is a different model…flat out. I think you’ll like it :)

At any rate, as I dig in more, expect me to post more (like I used to); and as tools become available, I’ll try to let you all know about ‘em ASAP!

In the words of my friend John Smith (Xbox team)…peace.

Hegenderfer

WM 6.0 and 6.1 Support in Windows Marketplace for Mobile

hegenderfer — Tue, 14 Jul 2009 19:28:31 GMT

If you haven't heard the news already, we will be supporting WM6.0/6.1/6.5 in the Windows Marketplace for Mobile. This is great news for app devs, as it gives you all over 30 million sockets that are already existing world wide :)

Here is Todd Brix's blog entry around the announce.

Windows Mobile Marketplace FAQ...and good news :)

hegenderfer — Mon, 30 Mar 2009 19:17:16 GMT

The Marketplace team has just announced some more details around the 'Windows Marketplace for Mobile', which I think is great news:

Q: Do I need to pay the $99 fee again to submit an application update?

A: No, if your application has been previously certified and published in the catalog, you can submit subsequent updates without incurring any additional fees. The application update will be made available through Windows Marketplace to all customers that have downloaded your application in the past.

Q: I previously heard that you only had 7 days to submit a free update. Has this changed?

A: Yes, we originally communicated that only application updates submitted within 7 days of their publish date would benefit from a free submission. After talking to the developer community and better understanding the dynamics and frequency of application updates, we have decided to extend the original 7-day window and make it permanent. This means that if an application has been previously approved in the marketplace the developer can submit updates to it without incurring any additional fees.

WAHOO!

We hope to get a good FAQ around the Marketplace up on the developer.windowsmobile.com site ASAP, so hang tight.

Also, expect more details in the coming weeks and months around this at developer.windowsmobile.com...

Tech Days and Windows Mobile Development

hegenderfer — Sat, 28 Mar 2009 03:57:16 GMT

If you are planning on going to Tech Days, there will be a pretty good line-up of Windows Mobile sessions:

Developing Mobile Applications with Visual Studio 2005/2008

Abstract:

Visual Studio 2008 brings lot of improvements for mobile developers, and Windows Mobile 6 SDKs tools that allow developers easier and faster solution development. This session will show you how to effectively develop Windows Mobile client applications. You will see some of the cool features that can be easily used in you applications, such as POOM integration, SMS interception, state and notification broker and camera integration. Session will be packed with live demos and code samples.

Using SQL Server Compact Edition for Data Storage and Synchronization in Mobile Applications

Abstract:

This session explains how to program SQL Server Compact Edition 3.5 SP1 for use as a fast, queryable local data store. You will learn how to use SQLCeResultSet objects as the fastest way to access data in a SQL Server Compact Edition database, and outline how to use LINQ to Objects to access data from the database. Finally, you will learn how to use SQL Server Compact 3.5 as the client-side datastore for a data synchronization solution using merge replication or Microsoft Synchronization Services for ADO.NET solution, and some tips for effective usage.

Windows Mobile Performance and Power Optimization

Abstract:

Windows Mobile Devices have a lot of processing power. However, when you are developing applications for Windows Mobile Devices you have to be aware of the fact that devices are battery powered and have less resources then desktop computers. In this demo filled webcast Maarten Struys explains how to create great performing applications that are not consuming too many system resources and that do not drain the battery. Using the ideas presented in this webcast not only allow you to create better applications, your end users will also get a better experience because your applications will look snappy and will help preserve battery life.

Win32 and .NET: For Windows Mobile, Which, When, and Why?

Abstract:

The Windows Mobile platform offers two core APIs. Each has its strengths and situations when one makes sense over the other. This session provides a framework for selecting which API makes sense, when it makes sense, and why each choice makes sense for the given scenarios. This session provides details that will ensure that you never feel at a loss when encountering this question.

Windows Mobile Web and Widgets: Leveraging web technologies to build experiences for Windows Mobile

Abstract:

The last few years have shown people the power of having a full-fledged web browser on a mobile device. From content providers building dedicated mobile sites, to cheaper mobile data tariffs, mobile devices have usher a new era of content an experiences available on the go. A new programming paradigm called mobile widgets has emerged in response to these recent trends. Widgets enable web developers to write application-like experiences that run outside of the existing browser, but are powered by the same technologies [HTML, JavaScript and CSS]. Gone are the days of building WAP sites. By leveraging the capabilities of a fully fledged browser on windows mobile, web developers can now build rich experiences for mobile devices without resorting to native/managed code. In this session, members of the windows mobile widget team will give you a sneak peek at the upcoming widgets platform. They will demonstrate how easy it is to develop widgets that mash up existing web technologies in novel ways.

Distributing and Monetizing Windows Mobile Applications through the Windows Marketplace for Mobile

Abstract:

This session presents developers with a unique opportunity to understand the next generation of Windows Mobile application distribution: Windows Marketplace for Mobile. Windows Marketplace will revolutionize distribution of Windows Mobile applications, games, and content, and is designed to solve the two largest problems of the Windows Mobile consumer-focused developer community: distribution and monetization. This session will provide application developers with the insights, tools, and processes necessary to begin distributing and monetizing their applications on the Windows Mobile platform.

Creating Compelling and Attractive UIs for Windows Mobile Applications

Abstract:

We explain how to utilize the Alpha blending and Gradient drawing APIs on the Windows Mobile platform to create a compelling and attractive user experience in your mobile applications. We also provide an example of how to create a framework that could be used to simplify the development of custom user interfaces

Good Business Week read about Windows Mobile and the challenges ahead

hegenderfer — Wed, 11 Feb 2009 03:54:28 GMT

If you didn't catch it already, here is a good read about Window Mobile and the catch-up game that we need to play.

"We're going to double-down on the Windows brand," says Todd Peters, head of marketing for Microsoft's mobile communications business. He says to expect a major advertising push. "When people go shopping in the future, we want them to ask specifically for a Windows phone."

A different direction. Coupled with some of the announcements we will be making at MWC, this should be great news for ISVs and partners who build apps for WinMo devices.

Windows Mobile is a Viable Mobile Platform

hegenderfer — Sat, 06 Dec 2008 04:25:36 GMT

Here's a fun read from Michael Gartenberg

--------------------------

Media Bistro, Michael Gartenberg, December 5, 2008

http://www.mediabistro.com/mobiledevicestoday/on/windows_mobile_is_a_viable_mobile_platform_101732.asp

"Last week, I jokingly suggested that Microsoft's Zune was the Rodney Dangerfield of tech. I was wrong, I think it's Windows Mobile that like Rodney, is lately, getting no respect...making the right choice of platform and device is a decision that has many factors for both business and consumer users, Windows Mobile should be on any of those decision short lists."

“I Like Windows Mobile and Am Not Ashamed To Admit It”

hegenderfer — Fri, 31 Oct 2008 02:58:37 GMT

Full text of the article and links below :)

-------------------------------------------------------------------

I like Windows Mobile and am not ashamed to admit it

ZDNet, Matthew Miller, October 30, 2008

http://blogs.zdnet.com/cell-phones/?p=214

A couple weeks ago Om Malik wrote an article in the NY Times titled, Why Windows Mobile is in Trouble, and most of the focus was on how the T-Mobile G1 and Google Android poses the biggest threat to Windows Mobile. The article gives an honest assessment of where Windows Mobile is at this time and concludes by stating that Windows Mobile is not a lost cause, but does need to take some actions to stay current and relevant in the mobile space. I agree with this bottom line, but also don’t think Microsoft has too much to worry about with the first Google Android device (the G1). I have been using the G1 for two weeks now and while it is great to see a mainstream Linux mobile OS, I am also heavily using my Treo Pro to get things done and stay in touch on the go. I don’t see a lot of people standing up and saying they prefer and like using Windows Mobile, but I know there are lots of people out there that do enjoy using this platform and I am one of them. I have read many comments online recently where people are trying to figure out if they want an iPhone or a new BlackBerry, but rarely hear that they are even considering a new Windows Mobile device.

If you just look at the specs, Windows Mobile may be considered the most powerful and functional platform out there (S60 also may take this title). However, as Microsoft is learning it is not just about the specs, but today people want the overall user experience to awe them. Honestly, HTC and Samsung are working to bring this type of experience to people, but the message just doesn’t seem to reach people like it does with the iPhone.

There are some incredibly powerful, diverse, and fun devices available in the Windows Mobile world, including the HTC Touch Pro, Samsung Epix, HTC Touch HD, Treo Pro (my current favorite device), Samsung OMNIA, Blackjack II, T-Mobile Dash, and many, many more. IMHO, one of the strengths of the Windows Mobile platform is that there are devices available in all shapes and sizes so that everyone can be satisfied. And as a mobile phone enthusiast, I love that I can dive into the details of the operating system and tweak away to my heart’s desire.

Then again, the sheer number of devices may also be a weakness because there is no central way that the platform is being marketed. Apple and Google have it fairly easy with a single device to promote from a single manufacturer. Almost all S60 devices come from Nokia so even though there are a number of different models, there is a single company name behind them all. With Windows Mobile you have manufacturers (like HTC, Samsung, and Palm) and wireless carriers (like Orange, AT&T, Verizon and T-Mobile) that have branded devices so it is extremely challenging to get out a consistent message. Microsoft also changed the naming scheme from a more consumer-friendly Pocket PC or Smartphone to Windows Mobile Smartphone that just doesn’t have the same ring to it. I think Microsoft can do a much better job of marketing some of the incredible strengths of the platform and maybe they should focus on things like Exchange support (for enterprise customers) and smart dialing (for consumers).

Windows Mobile has been around for quite a while and in the beginning (2000) the devices were buggy and unstable. I can honestly say that almost all the devices I have been using the last couple of years have been rock solid. I can count on one hand how many times my Windows Mobile devices (among them the T-Mobile Dash, T-Mobile Shadow, Treo Pro, HTC Touch Diamond, and HTC Advantage) have soft reset on me and I constantly check out new 3rd party applications and push the limits of my devices. I do find the non-touch screen devices to be a bit more responsive (except for my Treo Pro) and stable than the touch screen devices, but my experiences indicate stability and reliability is no longer an issue. However, this stigma still seems to be attached to Windows Mobile and is thrown around like a fact years later.

I also think Microsoft should have been the first to come out with a hosted Exchange option for consumers, just like BlackBerry has with its BlackBerry Internet Services for consumers or BlackBerry Enterprise Services for businesses. Microsoft could have done the same thing back when Exchange ActiveSync support was provided and consumers could have had a “BlackBerry-like” experience right out of the box when picking up a Windows Mobile device from a wireless carrier. Today, the iPhone has this with MobileMe and the G1 has this with Google, but Microsoft still should consider this even though some may say they are copying others. Nokia is moving this way with their Ovi initiative and it isn’t too late to show consumers they can remain connected with a Windows Mobile device.

A new Windows Mobile site has launched called Windows Mobile Developer Network and shows you upcoming events, featured applications, Windows Mobile team websites, and featured content articles along with a bunch of other content that helps people use their device to the fullest. The site is designed to aid developers in bringing applications to Windows Mobile, but is also useful for just about any WM user. The Windows Mobile Catalog page is a nice way to browse some of the thousands of applications available for Windows Mobile devices and links to multiple vendors so you have a single consolidated location to see what is out there. Creating a site like this for consumers that is promoted in the box, along with a hosted Exchange service could help Microsoft reach more people with Windows Mobile.

As far as the enterprise user goes, I prefer and use my Treo Pro with my new work Exchange server and absolutely LOVE the experience and functionality. Some people may call me crazy, but I actually prefer using my Treo Pro to interface with my Exchange account (creating appointments, adding contacts, and checking email) rather than using Outlook on the desktop most of the time. Windows Mobile should be dominating the enterprise market and it would be interesting to see study results looking at mobile devices in businesses rather than across the entire spectrum of the mobile community.

I also enjoy using 3rd party applications on my Windows Mobile devices that allow me to work and play both online and offline. There are applications to meet just about every need out there and I do not have to make any compromises with software or connectivity with the latest Windows Mobile devices. Pair a Windows Mobile device with a REDFLY and you even have a powerful mobile computer where the display and keyboard sizes don’t really limit you anymore.

I also like using devices running S60, but find the PIM and email experience to be superior on Windows Mobile devices. If multimedia creation is a major factor in your purchasing decision, then S60 is definitely the winner in this category. There is also a failure to market S60 successfully in the U.S., but that may largely be driven by carrier support and I’ll save more thoughts on S60 for another post.

iPhone alternatives on Fox News

hegenderfer — Thu, 28 Aug 2008 22:15:51 GMT

Okay, so normally I would be the LAST person to recommend anyone actually go to Fox News, but our very own Scott Rockfield was on the Fox Business Channel this morning talking about Windows Mobile and the alternatives to the iPhone.

I've talked about our public perception on this blog in the past (or total lack of in some cases)...but we are starting to get the word out there. I am confident that we'll be running some very interesting stuff in the months to follow. Sure, this is a small step, but it's at least a first step. Stay tuned...

The Windows Mobile Ecosystem for Developers

ReedR — Wed, 23 Jul 2008 00:18:00 GMT

July is a special time around Microsoft. It’s the start of a new fiscal year… which is kind of like the calm after the storm. A few weeks ago, this place was nuts…closing out business, writing performance reviews…clock ticking, time running out to meet those metrics. Once July hits, it’s a brand new game. A ‘tabula rasa’ or sorts. People take some vacation, breath deep for a change, focus their thoughts, and prepare for the re-orgs and business directives that always shake things up as we start again. In some ways, it’s like starting a new job every year and there are always unexpected surprises. It’s also a good time to tackle a post I’ve been wanting to do for awhile..

I field a lot of developer questions around Windows Mobile. Most are straight forward technology inquiries, but there are a number of topics that always lead to discussions about the Windows Mobile ecosystem and our relationship with device makers and operators. For example…

· When will the latest version of Windows Mobile be available for my phone?

· Why do some devices have features that others do not (e.g. - Camera quality, video codecs, available RAM & storage, etc.)?

· I found a bug… when can you fix it?

· How do I disable the security on this device?

· I’m building a SIP/VOIP client and want to integrate it with the phone.

· etc…

It’s an Ecosystem
On one hand, the diverse ecosystem of Device makers, Operators, and Independent Software Vendors (ISVs) creates a healthy pipeline of choice, opportunity, and competition. It’s is a core strength of our platform. On the other hand, the ecosystem comes with some clear (and not so clear) areas of ownership. It’s an important topic for developers to be aware of. I thought it might make an interesting post.

Desktop vs. Windows Mobile
We do our best to create an open platform that is accessible to everyone. Developers can use the same tools and technology they are familiar with (e.g. - Visual Studio, .NET, Win32). They don't have to jump through hoops or qualify for SDKs. Device makers all get the same platform building blocks from us to work with. This allows them to create new and innovative devices based on their industry expertise. ISVs are free to build anything they can dream up using the platform SDKs to run on those devices. The success of any platform depends on everyone working together from a pool of opportunity and the expertise they bring to it. Mobility is a big, big pool right now. The touchy part of any ecosystem comes into play when you start getting into "ownership". Who owns what.

With desktop PCs, you can pick and choose from a plethora of hardware vendors to find the best model and value for your needs. The machine may come pre-configured, but if you want to rebuild it yourself – upgrade the OS, reconfigure the system… go right ahead. You have complete control over the Windows installation on your home PC. Your PC manufacturer might own the BIOS but everything else typically loads from disk storage, so it’s very easy to change things around. This is the model most developers are used to.

Windows Mobile evolved out of the Windows CE model and it’s a very different animal from the desktop PC. CE is a highly customizable and componentized OS, designed for device makers to adapt to any kind of hardware they might produce. “Devices” may not even include storage or a display. CE is designed to work with small memory footprints, so device makers control the decision over what components are included in the device ROM. They could include ONLY the things they needed and save memory by leaving out the stuff they didn’t. That’s great for custom devices, but bad for developers who need a predictable API set and users who need a consistent experience. Windows Mobile is a Microsoft defined CE platform. While we let device makers customize many, many areas – we define base platform requirements that must be met, add a special shell, some core phone and platform applications, and enforce a logo test that device makers must pass before selling as a “Windows Mobile” device. This provides a consistent API set for developers who want to build applications and a consistent user experience as a marketable device. Unlike a PC, the platform still has to be adapted into a device ROM and the device maker is the only person who can do that. We can install an update to persistent storage, but we can’t permanently patch a device maker’s ROM. Only they can do that.

Who Owns What?
When you see an announcement like “Windows Mobile 6 was released today” and wonder why it takes 3-6 months before you see a device in the market, it’s because a lot of work has to happen to go from platform release to the commercialization of a device. The device might say “Windows Mobile” but Microsoft just a part of the team that makes it happen. At a very simplistic level, the release cycle looks something like this today:

1) Microsoft releases Windows Mobile Platform X.X and Adaptation Kit to all licensed device makers

2) Device makers “adapt” our platform to their new hardware (adding radio & drivers, power management, system plumbing, software customizations, select optional components, etc.) to create a Windows Mobile device they can sell through Operators

3) Operators negotiate with device makers to choose which devices they think will bring business to their networks

4) Device makers & Operators work together to “brand” chosen devices, include operator specific software/radio, decide on default security model, etc.

5) Devices must pass Microsoft logo testing to meet base level device quality and experience and carry the “Windows Mobile” brand

6) Devices must pass Operator acceptance testing and pre-market prep (sales, support, training)

Once a device is in market, the we continue to release updates on a regular basis to Device makers...

1) Microsoft releases Adaptation Kit Updates (think Service Packs for Windows Mobile) as well as new platform releases to Device makers

2) Device makers and Operators make a business decision on whether to build, test, and provide updates to devices in the market

Why It Matters to Developers
Why does the ecosystem matter? Understanding the release cycle helps makes sense of some of the questions around updates, features, bug fixes, and configuration differences you see with device out there. Those are universal questions that apply to both developers, IT, and end-users.

I also mentioned ”areas of ownership”. ISVs often build their business around technology “gaps”… needs that are not being addressed by anyone else. I touched on this a bit in previous blog posts with undocumented APIs. As part of the adaptation process, Device Makers have access to some APIs and customizations not found in the public SDKs. This includes areas like the phone application/canvas, cellular radio APIs, Wireless Manager, DRM, VOIP/SIP, driver development, and low level power details, etc. Most ISVs don’t develop in these areas, but some (e.g. – integrators, peripheral makers, security vendors) do. ISVs that would like to work in these areas need to have sponsorship from a licensed Device Maker who can help them get access to this information where applicable.

Rude Q&A

When will the latest version of Windows Mobile be available for my phone?
That’s a business decision that is entirely up to your mobile operator or your device maker to provide an update.

Why do some devices have features that others do not (e.g. - Camera quality, codecs, available RAM & storage, etc.)?
We enforce some very basic requirements to ensure a device meets a quality bar before it’s branded “Windows Mobile”, but we also leave a lot of room for Device Makers to make those decisions. As a result, you can find Windows Mobile consumer devices in just about every price range and specialized devices for every industry. Device makers choose to make hardware decisions for a number of reasons – cost, target or operator market, memory & driver footprint, etc. Choice is a good thing.

I found a bug… when can you fix it?
Please report it. Microsoft Support does not charge for support cases that are determined to be caused by a bug in our platform and we can’t fix what we don’t know about. Always test it on the emulators and also a comparable device by another manufacturer if you can. If it doesn’t repro (reproduce) in the emulator or a comparable device, it may be a device specific device problem that needs to be reported to the operator or Device Maker. When we fix a bug, that fix typically goes into the next platform update we release to manufactures or they can specifically request individual hotfixes. Bottom line though-- it’s up to the manufacturer to produce an update for their device. If it is a bug in our code, we’ll do our best to help you work around it outside of a manufacturer update.

How do I disable or change the security settings on this device?
Security is initially owned by the Operator (or whoever sells the device). If they don’t have their own root cert on the device, then they may defer to the Device Maker for control. If you are an administrator, you can look to Exchange or SCMDM to help enforce security policies but as a developer, your options may be limited for 2-tier (Standard) devices. See my previous post on Security for Developers.

I’m building a SIP/VOIP client and want to integrate it with the phone.
Anyone is welcome to build a stand-alone client, but in order to integrate with the existing phone application, you need to be working with a licensed Device Maker.

Do I need to be working with a Device Maker to build a LAP?
No, LAP documentation has been released as part of the public Windows Mobile SDK.

What tools do I need to build drivers for Windows Mobile?
In theory, the model isn’t much different from CE and it’s possible to build a driver using Visual Studio – however, it’s not supported unless you are working with a Device Maker and have the proper level of debug tool and documentation.

Additional questions posted by readers…(thanks for the feedback)

Why developers should create software for Windows Mobile if they have to pay 50-60% of fee to intermediary [software distribution] companies … while Apple takes only 30% ?

Developers are not required to pay anything to distribute software on Windows Mobile. Many ISVs take orders off their own web site and distribute corporate apps without ever talking to someone from Microsoft or a distribution partner. The real question is how do you maximize your sales reach? Is it worth paying a software distribution portal to help you reach a larger audience? Many developers think so and this is also an open ecosystem. Software distributors set their own prices and many offer a sliding percentage based on the number of sales they help you make. You can pick the distributor that provides the best deal to help you reach your audience or do it yourself. Competition is a good thing. We don’t force you to sell through Microsoft. A good place to start looking – the Windows Mobile Catalog, which links to several distribution partners. If you choose to list your apps in the Microsoft catalog, we can share that information with our distribution partners and help you extend your reach.

Why still it is not possible to purchase Windows Mobile software from within Windows Mobile - like it is with iPhone ?

It is possible. There are actually several on-device software catalogs out there that allow you to purchase apps right from your phone. Operators sometimes add this in and most of our distribution partners provide client catalogs you can run from your phone. We have a lot of distribution partners and channels to get software so forcing a device to use ONE or list ALL of them doesn’t really make sense. Operators can preconfigure their devices with the client of their choice if they want to go this route. Would it be easier to have a single point of software distribution for everything to make it easy on end-users? Maybe – but as a developer, I don’t really like the idea of being locked into a single distribution channel. Our partners deserve some options. We do hear this a lot though and it’s something we’re working on to make purchasing easier on end-users.

On a Final Note
For some ISVs, this post will be a big snoozer. For others, this is a big deal. Anytime I get into the ecosystem discussion with ISVs, I try to pick my words carefully. Most of the time, it’s a developer who wants to re-engineer some part of the platform that only the Device Maker has access to. Sometimes you need to work with the Device maker…sometimes we can help. We originally did not expose LAP interfaces to ISVs. Our security ISVs set us straight and now it’s public info. My goal is to help share knowledge with those that have struggled in this space and get some good feedback. I also want ISVs to understand the ecosystem so they can help influence it in the right places. I hope this info helps.

Best Regards,
Reed