Tag Archives: windows phone

microsoft, mobile, nokia, professional, software development, visual studio

Developing for Windows Phone: what’s new

2 Comments

One thing that is easy to overlook in all the talk about Windows Phone, Nokia, and Microsoft’s prospects against iPhone and Android, is that the Windows Phone developer platform has substantially improved with the 7.1 SDK – the phone is 7.5 but the SDK is 7.1, just to confuse you.

Here are a few highlights from the list of what’s new:

Multitasking. Apps still do not continue to run when they do not have the focus. However, Microsoft has implemented several features to make it look as if they do. This includes background agents, background audio (another kind of agent), scheduled tasks, background file transfers, and fast application switching. Although apps do not execute in the background, they do stay in memory if free space allows, so that resume is near-instant.

Silverlight 4. The version of Silverlight implemented in Windows Phone is now Silverlight 4, though there are some differences between Silverlight on the desktop and Silverlight on the phone, including the fact that there is no Silverlight in the browser.

Apps that combine Silverlight and XNA. You can now render both XNA and Silverlight content in a single combined Windows Phone app.

image

Visual Basic and XNA. XNA was C# only in the initial release. No longer.

Better sensor support. You can now access the compass and gyroscope, and use a combined motion API.

Socket support. Use TCP and UDP socket protocols.

Network information. This is actually critical to creating well-behaved apps. New network information classes let you get network status and capabilities. You can also register for network availability change events.

Two-sided Live Tiles. Live Tiles in Windows Phone have two sides and flip automatically, effectively giving more space to show information.

Advertising SDK. Sign up to include ads from Microsoft Advertising in your app.

IE9 WebBrowser Control. You cannot embed your Silverlight app in the browser, but you can embed the WebBrowser control in your Silverlight app, now with IE9’s fast Javascript and HTML 5 features.

Local Database. A local database API is now included in Windows Phone. Sadly this is not Sqlite; I’m guessing it is a variant of SQL Server Compact Edition. You access and manipulate data with LINQ to SQL – no Entity Framework ORM (Object Relational Mapping) on the phone, though LINQ to SQL is also an ORM framework. There is no way other than LINQ to execute SQL locally.

New Launchers and Choosers. Launchers and Choosers let your app present picklists from data stored elsewhere in the phone. You can now choose an address, invite players to a game session, show a location on a map, or show map directions.

Read-only access to Contacts and Calendar.

Encrypted credential store. This enables you to store login details securely using a built-in API.

Programmatic access to the camera. This includes real-time access to the raw frames so you can create apps that use the camera.

Pictures and Search Extensibility. This lets your app interact with the Pictures hub and with the built-in search. Users who search Bing can launch your app from the results if there are matches.

New on-screen keyboards. There are now specialist keyboards for numbers and formulae.

Additional language support including East Asia. Overall there are 16 additional cultures available including font support.

Overall it adds up to a major update for developers. If you tried the first Windows Phone SDK and found too many annoyances, it might be worth a second look.

Is this the best mobile developer platform? I had this discussion today with Keith Varty, developer evangelist for Nokia. After rather enjoying a brief go with Xcode for iOS, I am not sure; there is no simple answer. It is certainly a candidate though: you get the excellent C# language, the mature Visual Studio IDE, and strong frameworks for both form-based and gaming applications. Then again you may miss those beautiful iOS controls.

gadgets, mobile, smartphones

What will it take to make Windows Phone a success?

Microsoft made a splash in New York City yesterday with a giant Windows Phone in Herald Square.

image

The idea I guess was to show how each “Live tile” is a window into a feature of the device, with a special emphasis on “people” – the way Windows Phone aggregates Facebook, Twitter, LinkedIn, Windows Live and more into a single feed and tile.

This is the kind of stunt you get when a huge corporation with a lot of money to spend is trying to muscle its way into a market.

Is it enough? It does feel as if Microsoft has managed the re-launch of Windows Phone better than its first effort around a year ago – the first devices went on sale in October 2010. The operating system has been tweaked, the new devices are more imaginative, and partner support seems better. I actually saw some window displays for Windows Phone in my local small town though they were gone a few days later.

It still feels as if Microsoft is fighting an uphill battle. There is not much wrong with the phones now, but what is the killer feature that will sell it alongside Android and iPhone? Personally I like the SharePoint integration, but Microsoft is still primarily going after consumers rather than business users.

There is also the matter of the tiles. They work well, but look at the photo above: are they beautiful? Not really; and it is unfortunate in some ways that all the Windows Phones look like this.

That said, I enjoyed my few minutes with an HTC Titan; it has an exceptionally large display and a great camera but does not feel too bulky, and I can see it doing well if the marketing is right. Nokia’s Lumia 800 looks good too.

Microsoft came late into this market though, persevering with its old Windows Mobile for too long, and it is not going to be easy to catch up.

mobile, smartphones

Something has changed for Windows Phone

3 Comments

When Windows Phone 7 launched last year, it was obvious that it could not succeed since it was all-but invisible to most people. In my local small town centre, which has several mobile phone shops, it was nowhere to be seen.

I went out to post a letter just now and was astonished to see this poster in the window of Phones4u:

image

I went in and discovered only a dummy of the Radar and Titan on display. I asked to see a Titan and they got one out for me to see.

The Nokia Lumia 800 was also on display, this one a working model.

image

The Titan has a gorgeous large screen, but while it is slightly bulky it is slim and does not feel heavy to hold. I put it alongside the Lumia; the Titan screen does look larger and better. Unfortunately I could not see the Lumia out of its clip. The Lumia does benefit from Nokia Drive (not working because no internet connection) and seems to be around £100 cheaper than the Titan. The Lumia also has the free British Airways app pre-installed.

I asked the assistant what she thought of Windows Phone and she said she had not tried it. I said I had an HTC Desire (true) and she seemed slightly puzzled about why I would want a Windows Phone though she thought it would be good for work because of Office.

Still, Microsoft’s device has visibility at last, though this seems to be more because of moves by Nokia and HTC than from Microsoft itself. If it can win the support and enthusiasm of some of those influential retail assistants we may see significant growth in market share.

.net, microsoft, professional, silverlight, software development

Windows Runtime must come to Windows Phone

1 Comment

I’ve been trying Windows Phone 7 in its latest “Mango” version over the last couple of days and mostly enjoying it. One thing I am not impressed by though is the range of apps available. Have a look at the Marketplace – Microsoft may claim 30,000 apps, but given how unexciting even the “top” selections are, you can imagine how bad the bottom ones must be. Microsoft I guess has been guilty of accepting almost anything to puff up the numbers.

What would fix this? Sell more phones, of course; but also improve the platform for developers. Windows Phone 7.x is not a bad platform: you get Silverlight, XNA, C# and Visual Studio.

By contrast though, the Windows Runtime (WinRT) shown at the BUILD conference earlier this month is a platform mobile developers can love. Here are what seem to me three great features:

  • Three first-class languages and programming platforms – C#/.NET, JavaScript and HTML 5, C++ and native code. All three are strategic platforms. I particularly like the native code option, as many mobile developers like native code and it is a weakness of Windows Phone 7.
  • Asynchrony built into the platform. This is a smart move: make every API call that might cause a delay an async-only call. On top of that, build easy async programming into the languages. The result should give apps a responsive user interface almost by default; developers will need to make an effort to freeze the UI.
  • Contracts which integrate apps with the operating system and with one another. There are five contracts: search, share, play to, settings, and app to app picking (for example, file selection).

Microsoft’s Windows chief Steven Sinofsky says Windows 8 is for tablets but not for phones. But he has to say that, because if Microsoft announced that the current Windows Phone 7.5 is a platform without a future, it would further dampen enthusiasm for the product.

Is there any reason why WinRT should not come to Windows Phone? A few:

  • Windows Phone is currently built on Windows CE, a cut-down version of Windows, whereas WinRT runs on top of the full Windows API.
  • The Metro-style UI is designed for tablets rather than phones.
  • Finally, the existence of Desktop Windows is presumed in the current Windows 8 design. If Microsoft has not had time to work out a Metro-style UI for something, you simply use the Desktop version.

All of these are good reasons why the arrival of WinRT on the phone will be delayed, but none are insuperable. Long-term, I find it inconceivable that Microsoft will persevere with a different programming platform for the phone and for tablets.

What are the implications for Windows Phone developers today? Well, WinRT and Metro borrow from the phone OS, so the porting effort should not be too bad, except in the case of XNA, a .NET wrapper for DirectX which WinRT does not support.

Of course this post is entirely speculative, and I have no insight into Microsoft’s plans beyond what is publicly stated, so there might be other compatibility options when and if the time comes.

And it is time that is Microsoft’s biggest enemy. Fumbling tablet computing has been a costly mistake, and the big question is whether anyone will care how good some future Windows Phone will be, if the ecosystem which Nokia likes to talk about is firmly established as Android vs Apple.

apple, cloud computing, iphone, microsoft, mobile, professional, windows

A few observations on Windows Phone 7.5 “Mango”

2 Comments

I received a Windows Phone running version 7.5 “Mango” for review yesterday. Here are some initial observations; I am not going to call it a review after such as short time.

image

There is still no screen capture utility – well, there is this one but it requires a developer accounts. So no screens, sorry. Microsoft should fix this – how difficult can it be?

Microsoft says there over 500 updates in Mango, and it does feel like a significant update, though retaining the look and feel of the first release. A half-version upgrade is about right.

Some things I noticed:

  • Task switching. Press and hold the back button, and swipe through running apps. This is excellent, better than iPhone or Android.
  • Voice control. This is expanded in Mango to include web search, text messaging and more. Tip: to see the commands, hold down the Windows key to go into speech mode, and click the help icon.

    It has great potential, especially with a bluetooth headset for true hands-free. I have a Plantronics Voyager Pro bluetooth headset, reviewed here. Using this guy, I can press and hold the call button on the headset, to put the phone into speech mode.

    I found this works well for calling people or simple searches, but general speech to text is not too good. I tried texting someone the message “Your parcels have arrived”. After several attempts, all of which were interpreted as various strings of garbage starting “George”, I gave up. I would still use it for making calls though; it seems that when the scope is narrowed to people in your contacts list, the interpretation is more reliable.

  • The search button is no longer contextual – it always takes you to Bing search. I think this is a retrograde step.
  • Local Scout is a feature that is meant to find restaurants, shops, things to do, and other handy information based on your location or the current map location. This is a neat idea, but when I tried it for my home town it did not work well. The first problem: I found that tapping the Local Scout tile is unreliable, and sometimes reports that Bing cannot find the location even when the location button in Bing Maps works fine.

    Fortunately you can also use Local Scout from Bing Maps. The Local Scout listing was not good though. Of the top 20 food and drink places, one had been closed for years, others were duplicated under old and new names, and there were hardly any ratings or reviews. Tap “Suggest changes” and you can submit changes to the address details or report closure, but you cannot add a review or rating, which seems a severe omission.

    I downloaded the TripAdvisor app which is a great deal more useful, mainly because of the amount of user-generated content.

    Maybe I’m missing something, but it seems to me that Microsoft needs to join a few dots here; Local Scout is only as good as its data.

  • Office and SharePoint integration. As soon as I gave Windows Phone my Live ID, it picked up my SkyDrive account and was able to open, edit and save documents there. I also hooked up Outlook to my own Exchange server, and added an Office 365 SharePoint account as well.

    SkyDrive support is new and a huge feature, especially considering that it is a free service. Editing features on the phone are limited, but you can include basic formatting.  More important, you can easily access what could be a large document repository.

    OneNote support is good, and notes made on your phone sync automatically to SkyDrive, where you can further view and edit them in a browser, or in desktop OneNote. I guess I can show a grab of the browser, which shows that the voice memo is inaccessible:

    image

    I discovered a few oddities. I was unable to link Windows Phone to my own SharePoint 2010 test server, receiving a message “We don’t support this authentication scheme”. Later I found this information:

Unless your organization uses a Microsoft Forefront Unified Access Gateway (UAG) server, you can only access a SharePoint 2010 site if you’re in the office and connected to your organization’s Wi-Fi network.

That is a considerable limitation. It did work OK with SharePoint on Office 365, except that for some reason I can find no way to create new documents on Office 365 – well, maybe in the browser. The Office Hub can create new documents on SkyDrive, but not on SharePoint, which is odd as the two have a lot in common.

Despite these issues, you get a lot out of the box for using Office on the move, particularly if you use a supported SharePoint configuration or SkyDrive. The on-screen keyboard is good too.

  • Music search. This is a fun feature. Go to Bing search, click the music icon, and it will try to recognize what is playing. It had no problem finding Katy Perry’s Teenage Dream. It struggled a bit with the more obscure Strangely Strange but Oddly Normal by Dr. Strangely Strange; but on the second attempt it found that too.
  • The social media features seem strong to me, though you are limited to the baked-in services which are Twitter, LinkedIn, Facebook and Windows Live (no Google+). You do have to link each service to your Live ID for full features; for example, you give permission to Windows Live to post to your Twitter account. The integration is smooth and if you spend your time juggling with these four services then this may well the phone for you. For example, you can post a message to all of them at once. I found the People hub good enough as a Twitter client.
  • Apps are still lacking. The issue is not the quantity of apps available, but their quality, and the lack of certain key apps. There is no official Dropbox app, for example, so you will need to use the web or a third-party workaround. On the positive side, the free Guardian app is great, especially since you can pin a section to the Start screen – I did this for Technology – and there are apps for WordPress, Amazon Kindle, the ubiquitous Angry Birds and some other essentials.

    I noticed that TripAdvisor has 61 ratings on the Windows Phone Marketplace, whereas the Android version has 39,930. That illustrates the scale problem Microsoft is facing.

  • Still no Adobe Flash.
  • Microsoft’s new Windows Phone site is clean and informative. Not always the case with Microsoft’s sites. The My Windows Phone site lets you find your, lock or erase your phone, once configured.
  • Internet sharing, which makes your phone into a wireless hotspot, is coming but subject to operator support and approval. This means you will likely pay extra for “tethering”. I have a free app which does this on my Android phone and find it useful, though whether it is worth paying extra every month is another matter.
  • Microsoft has introduced some features aimed at enterprises. In particular, Information Rights Management is now supported for Outlook and Office mobile documents. Another important feature is the ability to deploy custom applications as hidden apps, which do not appear in Marketplace searches, but can be downloaded from a link circulated internally. There is now a Lync (business messaging and conferencing) client for both Office 365 and on-premise Lync servers.

Future of Windows Phone?

My guess is that Microsoft is badly disappointed by the sales performance of Windows Phone to date. The problem is not so much the phone itself, but that it has failed to convince either the operators, or the retailers, or the general public, that it is something special and worth choosing ahead of either an Apple iPhone or Google Android device. In fact, typically retailers have few if any Windows Phones on display, and even customers asking specifically for one may be redirected to something else. The truth is, there is a disadvantage in having a minority-choice device, most obviously in the selection of apps available, but also in features that rely on user-generated content.

I asked about this problem at the Mango press launch and was told that the Nokia partnership will be the solution.

My review device is a first-generation HTC Trophy, and while it is decent enough it is not outstanding. Give Windows Phone some truly desirable hardware and a few must-have apps, and its fortunes will change, but that is not an outcome that I take for granted.

I do like the SkyDrive and Office 365 integration though, with the caveats noted above, and if I were Microsoft I would be pushing the value of those features.

mobile

Nokia results: demonstrating the Osborne effect?

1 Comment

Here’s Wikipedia:

The Osborne effect is a term referring to the unintended consequence of the announcement of a future product ahead of its availability and its impact upon the sales of the current product.

The reference is to Osborne Computer Corporation, a pioneer of early personal computers, which announced the next generation of its range long before it was available. Sales of the current model immediately dived, and the company went bankrupt.

In February this year, Nokia announced that it was abandoning its Linux-based MeeGo smartphone OS, then in development, and that Symbian would be reserved for low-end phones. Its future smartphone strategy will be based on Windows Phone.

Now here come the results:

The challenges we are facing during our strategic transformation manifested in a greater than expected way in Q2 2011.

says the release, which report an 11% decline in sales quarter-on-quarter and an operating loss:

In the period from January to June 2011, net financial expense was EUR 74 million (EUR 141 million). Loss before tax was EUR 141 million (profit before tax EUR 632 million). Loss was EUR 261 million (profit EUR 279 million), based on a loss of EUR 24 million (profit of EUR 576 million) attributable to equity holders of the parent and a loss of EUR 237 million (loss of EUR 297 million) attributable to non-controlling interests. Earnings per share was EUR -0.01 (basic) and EUR -0.01 (diluted), compared with EUR 0.16 (basic) and EUR 0.16 (diluted) in January-June 2010.

Would these results have been better, if Nokia had not bet its business on Microsoft’s mobile OS back in February? My guess is that they would. Nokia in effect announced the obsolescence of all its current Smartphone range. Smart device sales are down 32% year on year.

Still, even the Osborne effect does not account for the decline in its sales of feature phones, down 20% year on year and 25% quarter on quarter. This is what Nokia says:

The year-on-year and sequential declines in our Mobile Phones volumes were driven by distributors and operators purchasing fewer of our mobile phones during the second quarter 2011 as they reduced their inventories of those devices which were slightly above normal levels at the end of the first quarter 2011. In addition, our lack of Dual SIM phones, a growing part of the market, until late in the second quarter 2011 adversely impacted our Mobile Phones volumes during that quarter. Mobile Phones volumes were also adversely affected by continued pressure from a variety of price aggressive competitors.

Despite the grim figures though, it is too early to pronounce the failure of CEO Stephen Elop’s strategy. After all, no Nokia Windows Phones are yet on sale. The company must be hoping to hang on until it has a decent range of Windows Phones, and for Microsoft to grow its mobile market share dramatically above what it is currently.

Should Nokia have chosen Android rather than Windows Phone? Android’s extraordinary growth suggests that it should; yet there are signs of significant copyright and patent trouble for Android, and by attaching to Android Nokia would have been a me-too behind more established vendors such as Samsung, HTC, and nearly everyone else.

Should Nokia have persevered with MeeGo and Symbian? Although early MeeGo devices are winning praise, I doubt that the OS would have challenged Android and iOS; but that is open to speculation.

The problem for Nokia is that if it was going to make a radical platform shift, some degree of Osborne effect was inevitable. Adopting Windows Phone could not have been done in secret.

That said, perhaps the company could have been smarter. Rather than laying all its cards on the table, could it have announced a Windows Phone strategy alongside MeeGo and Symbian, adopting a more gradual approach to avoid shocking the market?

It is also worth noting that Nokia’s problems started long before the arrival of the new CEO. What we are seeing now is the playing out of old mistakes, not just the impact of what may be new ones.

However you spin it though, the new Nokia is a lesser thing than the Nokia of old, which commanded rather than followed the mobile market.

adobe, development, facebook, flash, microsoft, mobile, nokia, professional, software development, windows

Windows Phone “Mango” shown, looks good but still no Adobe Flash

4 Comments

I attended the London press briefing for Windows Phone “Mango”, also known as Windows Phone 7.1. This will be on new phones in the Autumn, and will be a free update for all existing Windows Phone 7 devices.

image

Microsoft showed a bunch of new features, including Internet Explorer 9 – which, we were told, is built from the same code as the PC version – improved social media integration now including Twitter and LinkedIn as well as Facebook, Hotmail, Exchange, Messenger and Gmail; and multi-tasking support.

Hold down the back key for a moment, and all running apps appear in a tiled view. Just tap the one you want.

We also saw text-to-voice and voice-to-text demos. The presented spoke the reply to a text message, though admittedly he chose to do a one-word reply, and sent it successfully.

Microsoft also announced three new OEM partners, Acer Inc., Fujitsu Ltd. and ZTE Corp.

It looks good; but I did have a sense that Microsoft is ducking the hard questions. One of those concerns Adobe Flash support. At a separate developer briefing, I asked developer relations guy Brandon Watson about Adobe Flash support, observing that when Windows Phone was shown in detail pre-launch at the Mix 2009 conference in Las Vegas, it was clearly stated that Flash would be on the phone, and that Adobe was being allowed to build the Flash runtime in native code, but that it would not be included at launch.

“It does not run on the phone”, said Watson. Then he added, “It does not run on the phone.” Finally, he said, “It does not run on the phone.”

Silverlight does not run in the mobile browser either, so perhaps the problem is with mobile IE – clearly not all the code is included. Or maybe Adobe is hanging back; I asked Adobe about this at Mobile World Congress earlier this year and got an answer that was warmer but no more informative. Or maybe Microsoft is thinking, Apple does not need it, so we do not need it either.

It is a shame though, because there is a perception that Flash is one of the advantages of not going the Apple route.

On the developer side, the beta tools for Mango were released today. You can target either Windows Phone 7.0 or 7.1 with the tools, so if the beta tag does not put you off you can get going straight away. There is a ton of good stuff for developers, including the SQL Server CE local database, and the ability to mix XNA and Silverlight in a single app. We saw an app from British Airways that makes use of this to show a 3D view of an aircraft cabin when choosing a seat; I am not sure how much real value this adds but it demos nicely.

The new emulator includes accelerometer support, so you can simulate movement to test your app’s response.

There is also a profiler which shows your app’s performance in various views. Code that you wrote is highlighted in blue in the graphical view, so you can tell what you can optimise, as opposed to slow system calls that are outside your control.

The developer tools are great though, and having played with a number of mobile developer toolkits I would say that Microsoft’s is among the best and above average, though I would like to see an option for native code development. “We hear that a lot,” Watson told me.

The problem though: developers want a big market, and so far Windows Phone has not delivered it. It is almost invisible on the high street, and all the current operators and manufacturers have other phones that they are more concerned about. That will change when Nokia devices appear, but in an intensively competitive market (not forgetting HP WebOS and RIM Blackberry/QNX/PlayBook) it will not be easy for Microsoft to gain ground.

After the event I discussed this with some of the Microsoft folk. Maybe the company can better exploit the Xbox link, and sell the phone to that community. Maybe Nokia will save the day. Maybe when Microsoft comes out with a fully professional iteration of Windows Phone, tightly linked to Active Directory and group policy, and with additional developer features aimed at line of business apps, maybe then it will take off.

One positive thing I heard today was an anecdotal report that returns on Windows Phone 7 are among the lowest because users like the device so much.

The social features in Windows Phone are already good and will be better in Mango – though bear in mind that by the time Mango phones appear in the Autumn, Microsoft will likely have iPhone 5 and many tempting new Android devices to contend with.

Years ago it used to be said that Microsoft had average products (or worse) but excellent marketing. With Windows Phone, the product is good but either the marketing is lacking or the task is too great. Of course there is still time, and this industry is full of surprises, but it will take more than Mango to make Windows Phone fly.

apple, smartphones

Photosynth for iPhone: capturing the unphotographable

We are having some unusually fine weather in the UK and I went for a walk in the Derbyshire Peak District yesterday. I was reflecting how hard it is to photograph wide vistas of countryside when I remembered that I installed the Microsoft Photosynth iPhone app a couple of weeks ago.

image

It really is easy to use: you just fire up the app, tap to start a new picture, and turn the iPhone to new positions guided by on-screen markers. When the iPhone beeps, hold it still and a new photo is added.

image

Panoramic photography is not new of course; my old Canon Ixus has a panorama feature. However, you have to navigate several menus to get the mode engaged, manually position the camera, and then use a separate application to stitch the images together.

The Photosynth app by contrast is great to use, and I have taken a landscape picture which I would never have bothered with before. My only complaint is that the beep can be hard to hear, but even if you miss it, the app does a reasonable job, especially in bright sunlight.

There are plenty of interesting images now turning up on the official Photosynth site – check the Mobile Panoramas section.

For more information see the official announcement post and video.

The point to ponder is why the app has come out first for Apple’s iPhone, rather than the company’s own Windows Phone7? Apparently a Windows Phone version is in preparation.

.net, google, hp, microsoft, mobile, professional, silverlight, software development, visual studio, windows

Windows Phone 8 will run Windows 8, with Silverlight centre stage?

2 Comments

More information on Windows 8 is leaking out now; and it gives some clues about how Microsoft intends to make sense of its two device platforms, Windows tablets and Windows Phone.

Microsoft held back from making its Windows Phone 7 OS available on tablets, which is why most of the numerous tablets being pushed out to compete with Apple run Google Android, and a few of them Windows 7 with its excessive power requirements and a user interface poorly designed for touch control.

Now the strong rumour is that Windows 8 supports two user interfaces, one that is tile-based like Windows Phone 7, and another that is designed for PCs.

In other words, rather than continuing with the Windows Phone 7 OS which is built on Windows CE, Microsoft will build a new version of the Windows Phone 7 UI on top of full Windows.

My further assumption is that Silverlight apps will still run on the new OS, providing continuity with Windows Phone 7 which uses Silverlight or XNA, both based on .NET, for its application platform.

Silverlight might also be used as the platform for apps delivered by the new Windows app store. This is Paul Thurrott, though reported as rumour:

Windows 8 will also include a new app model codenamed Jupiter that will target a new Windows Marketplace app store. The app store will provide access to new, Silverlight based "immersive" applications that are deployed as AppX packages (.appx). The Windows and Office teams are betting very heavily on this new app type, according to my source, and development has already begun using a beta version of Visual Studio 2012. These apps can be written in C#, Visual Basic, and even C++.

We do know that Silverlight 5 supports full platform invoke of native code, a feature which tends to support the idea that it is becoming a key runtime for Windows.

Let me speculate a little further. Imagine you are Adobe, for example, which has said it will deliver the Flash runtime for Windows Phone. Although it competes with Silverlight to some extent, Microsoft needs to tick the Flash box for Windows Phone. But why would Adobe want to invest in Flash for Windows CE, when this OS is not going to be used for Windows Phone 8 and it will have to write new code? I will not be surprised if we hear that Flash is now not coming until Windows Phone 8.

Even within Microsoft itself, I would guess that investment is focused on the next generation rather than the one that is destined to be short-lived.

One partner that is no doubt close to Microsoft’s plans is Nokia. If the above is correct, then Nokia is buying into the Windows OS, not the Windows Phone OS. Will Nokia wait for Windows Phone 8 before launching devices on the platform? I have no idea – and delay will be costly – but I imagine its main plans will be focused on Windows Phone 8 and the possibility of tablet as well as smartphone devices.

The immediate conclusions would be:

  • Silverlight is safe as a development platform, but only for Windows. See also Silverlight the new Windows runtime, HTML 5 the new Silverlight?
  • The Windows Phone 7 OS will be short-lived but the new UI should be a natural progression from what we have now, and apps should still run, so Microsoft can position Windows Phone 8 to users as a new version of Windows Phone rather than a change of direction.
  • Microsoft will not have a coherent mobile and tablet platform until Windows 8 ships sometime in 2012. Google, Apple, RIM, HP, all have plenty of time to establish their competing platforms.
adobe, java, professional, software development

RIM announces Java and Android runtimes for the Playbook, beta of native SDK

RIM has announced several new options for developing apps for its PlayBook tablet.

RIM will launch two optional “app players” that provide an application run-time environment for BlackBerry Java® apps and Android v2.3 apps. These new app players will allow users to download BlackBerry Java apps and Android apps from BlackBerry App World and run them on their BlackBerry PlayBook.

In addition, RIM will shortly release the native SDK for the BlackBerry PlayBook enabling C/C++ application development on the BlackBerry® Tablet OS. For game-specific developers, RIM is also announcing that it has gained support from two leading game development tooling companies, allowing developers to use the cross-platform game engines from Ideaworks Labs and Unity Technologies to bring their games to the BlackBerry PlayBook.

It sounds as if the Android runtime will not be perfectly compatible with real Android:

Developers currently building for the BlackBerry or Android platforms will be able to quickly and easily port their apps to run on the BlackBerry Tablet OS thanks to a high degree of API compatibility.

Nevertheless, this will be an attractive route for Android developers looking for a quick way to port to the Blackberry.

The native SDK is currently in “limited alpha release” but RIM is promising an open beta for this summer.

The BlackBerry Tablet OS NDK will allow developers to build high-performance, multi-threaded, native C/C++ applications with industry standard GNU toolchains. Developers can create advanced 2D and 3D applications and special effects by leveraging programmable shaders available in hardware-accelerated OpenGL ES 2.0.

The deal with Unity is important too. Unity is an increasingly popular toolkit for game development and adding the Blackberry to the list of supported platforms will boost its appeal. Ideaworks Labs makes the Airplay SDK, a cross-platform toolkit which already supports Apple iOS, Android, Symbian, Samsung Bada, HP webOS and Windows Mobile.

Note that the primary SDK for the Playbook has until now been Adobe AIR; and since the UI itself uses the Flash runtime this likely still makes sense for many applications.

RIM is doing a good job of opening up its platform. It is an interesting contrast to Microsoft’s “Silverlight, XNA or nothing” approach for Windows Phone.