This blog has, IMO, some great resources. Unfortunately, some of those resources are becoming less relevant. I'm still blogging, learning tech and helping others...please find me at my new home on http://www.jameschambers.com/.
Showing posts with label Windows Phone. Show all posts
Showing posts with label Windows Phone. Show all posts

Wednesday, March 23, 2011

How Windows Phone 7 Could Fail in Canada

Folks, let me start by saying that I love my Samsung Focus.  Everyone’s seen an iPhone by now, but you can still turn heads when you’re zipping through the home screen on a WP7 device.  The interface is slick, the apps you need are mostly in the marketplace and the cooler ones – I’m still waiting for the possibilities of augmented reality apps with video and compass APIs – are on the way.

The phone is well integrated into my other communication points, from email and messaging to scheduling and sharing, and though I’m a heavy user I’ve seen little by the way of bugs.

But I live in Canada.  And the sale of this phone platform to my friends will be tough.  It’s not because the platform isn’t great – and I do think WP7 phones are on a great platform – it’s because the phones in Canada are crippled.

The Show Me Factor

We are moving away from a people with music players to a people with multifunction devices that have music players on them.  At least, those of us with the ability to support a smartphone contract are.  Well, us and the teenagers whose parents spoil them, but I digress.  I had my first MP3 player over 10 years ago and haven’t missed it a bit.

But the music marketplace in Canada Sucks.  Yes, “sucks” with a capital “S”.  We have very limited choices in where we can purchase our digital content outside of the iVerse.  I’ve used Puretracks and played with the paid versions of some other services but not all the content I want is there and I’ve previously had troubles with DRM content on mulitple devices.

I want my family – we have four PCs all running Windows 7 as well our our Xbox 360 – to be able to use something more fluid within our ecosystem, connected to and built into the devices we use.

Including our phones.

Look, there’s going to be a point where people will have seen it/been there/done that and if the experience isn’t positive they won’t want to go there again.  There’s a really good, but shortening, window that Microsoft should be able to leverage.

The Switchover Debate

Look, if I can’t convince my wife, my soul mate, my partner until forever to buy a Windows Phone device then I’m not going to get too far with others.  These things should sell themselves, but this media marketplace keeps kicking WP7 in the face.

We’ve talked about the switch to a smart phone and she’s been leaning towards an iPhone for some time.  All of her music is in iTunes and we’d need to spend some time converting it (in some cases with DRM that might not be possible) and then we’d be left with the purchase void.

That chasm is too far to cross at the moment.  We’ve agreed to wait for a bit to see if the marketplace changes, but at this point it’s a wide open yawn’s worth of information available and no one is giving any updated information.  For fully three years we’ve been hearing “Keep checking the Zune web site for your region” and nothing more.

Challenge #1 - Marketing

I eagerly waited for the Zune HD here in Canada, only to have my hopes dashed when Future Shop pulled the remaining original Zune devices from the shelves.  A new employee said to me, literally three days after I almost bought one, that he’d never even heard of Zune.

What?!  How could that be?  How could the only device poised to be an iPod killer not even enter the general population’s vernacular? We are talking about a company who did the unthinkable here and broke into the video game industry, a move previously believed impossible as the market already had enough players.  How could, in this young and developing area with few serious players, Microsoft miss the boat with visibility?

The same thing seems to be happening with Windows Phone.  I can still walk into a room of people completely unaware that WP7 devices were actually out.

Challenge #2 – The Marketplace

This appears as #2 on my list, but not because it’s less important.  I will say this as directly as possible, Microsoft: the music marketplace must be fixed.

Technically, it’s not broken.  Because it’s not here.  This is the number one reason my wife won’t buy into the ecosystem, and it’s almost always one of the first things I’m asked of when I’m showing my phone.  You fire up Shazam and it’s right in your face: excellent execution followed by a lack of follow-through.

I am a sell out here, folks and I know it.  I’m a die hard.  This is a platform with great potential and I’ve even gone so far as to evaluate my “grey area” options (US credit card, friend’s address).  But I’d much rather see the ecosystem change for WP7 in Canada so that we can do things legitimately and without hassle.

I understand that there may be other problems.  I’ve heard everything from the CRTC blocking Microsoft, to third party licensing complications, to Apple threatening to make things messy.  But Microsoft hasn’t said peep squat about what the problems are.

Challenge #3 – Marketing

Yes, it’s the same as reason one, but different.  You see, the thing is that Apple didn’t sell it’s iPods to the millions of customers that have them.  The other customers did. Unfortunately, proud Canadians wielding their WP7 phones are ill-equipped to make the sale.

Heck, even the stores clerks aren’t really there as far as sales pitches.  When I asked to see the Focus at Future Shop, I was greeted with a, “Really? Why?”.  He was even more shocked when I took it home with me.

I’m not selling these phones and I don’t work for a cell phone company or Microsoft (yetWinking smile), but if a guy can’t convince his wife to get one, we’ve got a problem.  Shoot, I even convinced her to marry me, but I can’t pawn a phone on her!

The Fix

Actually, Fixes.  It’s plural.  Here are the things that can right the course for this beauty of a ship:

  1. Figure out the content licensing and make music available in the marketplace. If it’s a ways out, for now you must, must clearly communicate what the issues are.  Customers would be happy to lobby any group that is blocking the process.
  2. Set up Zune Pass now, even at a lower cost and with limited content. Get buy in from the Canadian content providers to get them in the streaming mix be it independent radio stations, the CBC, CTV or the sports broadcasters. Flesh out the product and give Canadians the same level of product that’s available in other countries around the world.
  3. Give out some more free phones.  Future Shop wouldn’t even let me play with one of WP7 phones until I said I was surely going to buy one.  They wouldn’t take it out of the box.  This is wrong and bad and a poor purchase experience and bad, too.  Apple has kiosks setup to demo different models of the iPod/Pad/Phone/Thing and for WP7 I get to look at a cellophane wrapped box? Boo!
  4. Increase visibility.  Get storefront space. Encourage cell phone dealers to use and promote the phone.  Roger’s booth in our mall here had the iPhone 4 announcement posters up six weeks before the phone was launched.  There is still nothing in the mall about WP7.  Nada.

I am a software developer and though my previous experience has been on other platforms and technologies, right now I work exclusively on the MS stack.  I am going to MIX11 and am super pumped to see what the year ahead will bring us.

I’ve already come to terms with the fact that most of my concerns will not be addressed by the time the event rolls around, but you can be sure I’ll be sharing my thoughts with whomever will give me an audience.  Basically, it’s a conference where I’ll be hanging out with a ton of folks who’s phones are cooler than mine; sadly, we’ll have the same phone.

This is a phone that can really give customers a fresh experience with a unique level of integration with communication, search, maps, gaming and social networking.  I really hope that WP7 survives in Canada long enough to bear the fruit it is longing to produce.

Thursday, March 3, 2011

Windows Phone 7 Wishlist #3

There are two things I am looking forward to in a big way, but not on my wish list (because these will be realized for sure):

  1. The upgrade to HSPA+ in my area, and,
  2. The Windows Phone 7 first update.

I’ll get to my wish list in a moment.

I am stuck on the Edge service network because of my locale. The towers were upgraded months ago, but one of the partners in the carrier network (not mine) have equipment and services and software older than bunk and they can’t flip the switch until everyone’s ready. This is going to happen in days and I can’t wait until I’m pulling down 7Mbps on my phone.

I have a Samsung device and have not yet received the update. I’m not sure if it’s a candidate thing, or a rolling update thing, or even if my carrier is blocking it (I’ve heard all three) but I am looking forward to the pre-update update that is currently in the works, especially as it paves the way for The-Big-One in the next few weeks.

I wondered here if my carrier might be blocking the update, but I don't think that could really be the case. The phone checks for updates, likely directly to a WP7 service, and the device itself is updated through the Zune software on PC.

Here’s My List

  • I would like a way to search my text messages. This is present in mail, so it seems like it’s not too far fetched in texts. I had someone text me the phone number of my friend ‘Mike’, but I couldn’t remember who sent it to me. The text was something like “Hey Mike’s new cell is…” so I should have been able to find it fairly easily.
  • I would like an editor for my alarms and ring tones. Build it into Zune, or make a Windows Live ZuneTone application that you can download and make your own ringtones and alarms. Let me set cues for vibration. Let me shift pitch and even layer multiple audio tracks. Let me share it through Zune or Live or something with my friends.
  • A first-party, no frills sound recorder. The same level of function as the one built in to Windows 7. In fact, I would love it if I could also use the audio jack as a line in to record. I volunteer on a regular basis and work the sound board (or at least help) and I hate lugging around a laptop to record the audio.
  • Because I feel as strongly as I do about this, I’m going to say it again: Canadians want to pay for their content. Please make Zune Pass available in Canada. If this plea doesn’t work, I’m going to track down folks at MIX11 and talk to them in person! ;o)

I have a couple of other items on my list, as mentioned previously:

Friday, February 25, 2011

Windows Phone 7 - What if?

Nice. Looks like Microsoft is starting to ramp up the ooh-la-la with their advertising. Combined with the web-based ads with the head-to-head comparisons, the new Windows Phone 7 commercials are starting to look a little more playful.



Yeah. My phone does that. :)

Tuesday, March 23, 2010

Windows Phone 7 Series Development – Allowing the User to Choose a Photo

I am using the WP7 SDK from March 2010 at the time of this post.

I’ve been working on the SDK the last few days and am really enjoying it. I’ve hit a few roadblock in the ‘tasks’ department and am hoping to find a workable solution soon.

At this time, it does not appear that the emulator is ready for some types of application development and testing, specifically related to work in the Microsoft.Phone.Tasks namespace.

A little fun, first

image

I think it would be hilarious if everyone downloaded the emulator for Windows Phone 7 Series and started hitting Apple’s site from IE.

I don’t think they’d care, but it would still be funny.

MSDN Struggles

So, we have a few things to work from if we want to get the user to pick a photo. Say you’ve got an application that would allow them to send a photo to a friend or upload it to a service on the cloud.

The first thing they’ll need to do, obviously, is to pick the photo they want to work with. This actually looks like a trivial task.

In the Microsoft.Phone.Tasks namespace we have a series of helpers that give the user a consistent “Windows Phone” look and feel from within our applications. Here are some examples:

  • BingMapsTask
  • CameraCaptureTask
  • EmailAddressChooserTask
  • EmailComposeTask
  • PhoneCallTask
  • PhoneNumberChooserTask
  • PhotoChooserTask
  • SaveEmailAddressTask
  • SavePhoneNumberAddressTask
  • SearchTask
  • SMSComposeTask

We’re going to be able to offer a deep level of integration with the phone experience. Unfortunately, we’re working in a bit of a void right now.

The documentation suggests that, when executed, these tasks will return there results on the Page’s OnChooserReturn event. The signature is simply:

void OnChooserReturn(object sender, EventArgs e)

The single entry point concept here (all task results will come in on the same event handler) suggests that we’re going to want to use the Rx (Reactive) framework to sort out the details.

But how do we get at our result?

imageMSDN lists a ChooserEventArgs object that gives us access to the result. This is a generic class, with the task-specific result type defining the result. But how do we pull it?

There are no examples at this point, so I can only assume we’re going to cast it from the EventArgs we get in OnChooserReturn. We’ll use reflection to test (likely, this is where we’ll put Rx to work) then handle the result as appropriate.

As you can see from the emulator screen shot, I can’t go any further to test, explore or prove this as cannot execute the Tasks listed above with the current tools. Instead, we are presented with the following COMException:

The drive cannot locate a specific area or track on the disk.

The PhotoResult class (returned from the CameraCaptureTask and the PhotoChooserTask) will be the type I funnel in on when this functionality is lit up.

The Good and the Bad

I’m loving this direction. The Rx Framework is all about applications that live and respond to an environment and doing that asynchronously. Funnelling the results of environment actions by the user through a single event on a page allow us to behave that way as well.

Because we get access to the resultant object by overriding the event handler on the page, we will be able to have each page in our application respond differently – in context – when the event fires. I think this is a fairly clean approach and hopefully encourage developers to design specific contexts for their applications.

There are two negatives from my perspective right now:

  1. Lack of code samples – this one will work itself out. As the community jumps on board we’ll see the samples popping up. I hope I can contribute in this area, too. MSDN will also move towards a more complete state if Microsoft follows through on their commitment to developers in this space.
  2. Lack of emulator support – this will be a big pile of suck if it doesn’t get implemented. I’m hopeful that there will be an integrated photo store, or a way to push photos to the device in such a way that the emulator sees them as user photos. Also, emulated camera support would be great: let me specify a directory on the computer with photos in it, then choose a random one to return when I ‘take’ a photo in the emulator.

Early Goods

As is always the case when you get in early, the bits are tasty but not filling.

I highly encourage developers to get in on the scene here and push around the SDK.

And PLEASE, if you find out how to get the tasks working in the short term (in the emulator) let me know!

Friday, March 19, 2010

This is going to be a Great Ride

Scott Guthrie has posted the “hello world” for building a Windows Phone 7 Series app using Visual Studio 2010 and Silverlight.

imageAbout six months ago I did a pilot project on iPhone development and I must say it left me shaking my head. The IDE was, well, non-existent compared the mature MS platform.

Today, I wake to this blog post from Mr. Guthrie and I’m left shaking my head again: how will you be able to keep developers off of this platform?!

Simplicity and Complexity

If your mom passes away and a 15 year-old nephew says, ‘hey, it’s going to be okay,’ that’s simplicity before complexity. When it’s you’re great uncle, who’s lost his wife, his brother and outlived one of his children, that is simplicity after complexity and it means something completely different.

I think this is the story of development on smart phone platforms today.

The Objective C platform feels like a 15 year pimply kid. Microsoft’s message is quite different: “yeah, we get it.” And it is going to mean all the world of difference in the development world.

I can’t wait to get my hands on my upcoming Dell SX2210T to experience the full joys of this development story…

Tuesday, February 23, 2010

How Microsoft Will Win in the Mobile Phone Space

It’s no joke. Microsoft is finally in a place where they can and will compete hard with Apple’s iPhone and Google’s Android platform. As possibly the first company to figure out what it means to compete in this space – and certainly the first with real dollars to back their game – Microsoft has a big chance to win with Series 7.

Lessons from Xbox

image Microsoft came to the table with a gaming system in 2001 with some good juice. More than anything, they wanted to focus on making the developer story better than what was out there. They faced criticism on the size of the console, on the noise, on the size of the controller (which I loved, btw), on pretty much everything…but slowly they won developers over.

imageBy the time the Xbox 360 hit the streets, developers were singing the praises of development on the platform while Sony executives were just waiting for “smarter” developers who actually understood their technology to come along. In the first months of the Xbox 360 release, it became apparent that Microsoft was going to be the console that catered to the people who made games.

Interestingly enough, it seems as though Sony’s going to abandon the technology of the PS3 on their next console because we developers just ain’ts gots the smarts.

The biggest win was differentiation with the 360, not from other players, but from themselves. They reinvented what a product could like coming out of Redmond and it paid off in droves. It was rumoured that early designs were tested against focus groups without the branding, and almost no one was able to identify the manufacturer as Microsoft.

Lessons from Windows Mobile

You can can lead a horse to water, but you can’t make him drink. Especially if the water is acid and no one in the world wants to ride the horse anyways. And even more so because if you did want anyone to ride the horse, you had to make your own saddle and figure out a way to distribute the saddle on your own. And don’t expect any revenue.

RIP, Windows Mobile.

The development story was crap. Web service (cloud) integration was turd. Some level of expectation for hardware was non-existent, and you were just short of a demi-god if you could figure out how to get your app found. And unless you were a wizard-code-ninja working at HTC, good luck at making anything look good.

While Apple was making millionaires out of fart-generator authors, there were very few success stories in the fragmented, challenged development story on the Windows Mobile platform. Too many devices. Not enough support for developers. Little to no ‘dogfooding’ of the devices and content. Limited interim builds. Late and abandoned features and release dates. Inconsistent programming libraries.

And they’re leaving it all behind. I hope.

Where the Winner Is

image

I give it two years. In two years Microsoft will be shipping as many units as Apple. I am pretty confident in that number because of the lessons Microsoft should have learned from above.

That sentiment is furthered because of how they came through with Windows 7.

The argument is strengthened even more with the working prototype they put forward at Mobile World Congress.

Hubs are the new pages and clean is the new UI. Apps will be alive and the touch will be a productivity feature and user benefit rather than a scrolling gimmick.

What most people don’t realize is how much work Microsoft has actually done in this space. Apple didn’t invent the wheel here (I’m not say MS did, by the way). Tablets, touch screens, mobile devices…Microsoft has done so much wrong in this space for over a decade that they’ve learned everything you’re not supposed to do, and the very few, straight-forward things you need to do in order to compete.

But where they will really shine is in supporting developers.

By moving to XAML and enabling millions of developers already on the .NET platform to develop media-rich, touch-rich, dynamic applications from within the world’s number one IDE, Microsoft is set to roll a new story for what mobile applications can be (hint: not just fart generators).

Oh yes, if you want to develop applications that will run on millions of phones with an incredible user experience, standardized hardware and an open development platform, there’s an app for that.

It’s called Visual Studio 2010, and it will be the Achilles heel of the iPhone development story.

Tuesday, February 16, 2010

Microsoft Just Seriously Kicked Apple in the Nads

I am not joking.

If you’ve used a Zune HD – not just mocked it because it’s from Microsoft and because you love your iPod and have never actually used a Zune HD but it must suck because it’s not from Apple (all hail Steve) – then you know that they (Microsoft’s Zune HD team) have seriously got a pulse for how things should look and feel and work.

Well, that’s what they are bringing to Series 7, the new name and face of Windows Phone. It is freeking nuts.

image

The concept is a paradigm shift for anyone…well, anyone who uses a phone. We’re talking multiple pages of any-direction scrolling that actually makes sense and gives you a complete sense of being awesome.

Plus, it’s awesome.

The user interface is arranged as a series of canvases that allow you to finger your way around them. The canvas is bigger than the screen, and you just push it around to get where you’re going.

It is elegant, modern and by all early signs it is also fast, responsive and built to compete. Hard.

Another way to think of the user interface is the Xbox Live dashboard, optimized for touch. Heck, why stop there? IT HAS XBOX LIVE BUILT THE FREEK IN.

A good review of the upcoming game-changer is here:

http://gizmodo.com/5471805/windows-phone-7-series-everything-is-different-now?skyline=true&s=i

Here’s a snip:

The result is a feat no phone has performed before: Making the iPhone's interface feel staid.