in Search
Welcome to Neopoleon - Sign in | Join | Help
Navigation: Home | Forums | Galleries

iPhone vs. Windows Mobile - Apple vs. Microsoft - It's the Little Things

A couple years ago, I had an idea for a mobile app that would revolutionize the universe. It was innovative, solutionable, and coked to the gills with passion.

It was everything the World 2.0 wanted as well as a bunch of stuff it didn't.

I could have written it back then, but the tech required was a touch beyond what was available in most consumer mobile devices. It needed too many stuffs that weren't there. Like certain microchips and transistors and tubes and also magic and wires that are good.

Now, two years later, approaching the end of the first decade of the 21st century, in the year 2008, the technology is here, and it's in the hands of your average jackass moron mallwalker. And if it isn't already stuffed in your pocket, somebody at the mall will sell it to you on your way out of Forever 21 where, although you're only 13 years old, your boyfriend has just purchased $600 worth of lingerie for you, and your parents are Ok with it. If somebody can tell me what the hell's going on with today's youth, speak up.

I've been approached about producing the app. I haven't decided yet if it's what I want to be doing right now, but it's very tempting. To get a feel for what it would take to write and sell it, I've been doing a bit of research.

As far as hardware goes, I have options. The app has been designed to run in several modes. There's an active mode that requires a net connection and GPS. For the passive mode, all you need is a net connection. There's a possibility of doing a version for poor people that only uses texting, but that's a nice-to-have I won't bother with until the "real" app is done.

When considering which platform to use, there aren't many criteria (in my mind, for something sophisticated, the only sane platforms are the iPhone and Microsoft's Windows Mobile - if you aren't familiar with development for mobile devices, then just trust me when I tell you that developing for that crap "free" phone you got for "free" when signing your ten year service contract is hell on Earth):

  1. I'll target the platform that gives me the most access to your money. That means many people own the device, and there's an easy way for you to send me your money in exchange for A COMPUTER PROGRAM THAT WILL IRREVERSIBLY TRANSFORM YOUR WORLD FOR THE BETTER AND MAKE YOU FORGET ABOUT HOW MUCH YOU HATE LIFE.
  2. Because of hardware requirements, I'll target the platform that meets my needs and has the most uniformity across implementations. One of the hardest things about mobile app development is knowing what kind of hardware your users have. If there's a way of ensuring (more or less) that they'll all have the same hardware, then that way has an advantage.
  3. The better the distribution options for my app, the better for me. When you make something - such a piece of writing - every choice, at least if you're relatively unknown, involves compromise. Here, I can easily push whatever I want out to the web without editorial oversight or the fear that I'm going to piss off my investors. I'm not competing with anyone else for this space. It's guaranteed that my work, should I want it to, will, barring technical malfunctions due to my ISP being run by The Three Stooges, appear on the site (there's another compromise - if I were willing to pay more than, like, $3 a month for hosting, I could probably get service run by sentient beings). The trade-off here is that my site has nowhere near the reach of a big publishing house. You have to find my site accidentally or hear about it from your mother-in-law who's one of those people who've dedicated their lives to forwarding other people's mail to you. Somewhere in there is a "loook it this site is lolol called NFIPFOEOPOLEON.COMCOM." I'd much rather have the wider distribution, and if I knew how to get it, I would, but that doesn't mean I'd be equally excited about losing so much of my freedom to publish crap. These same compromises exist when distributing your app. You can do it on your own and have complete control, or you can use a distribution service. With apps, I'd much rather have the service, as I don't want to have to assemble the shopping infrastructure myself, and I don't want to wait for people to accidentally find me.

There's more to consider, but those are big time stuffs.

Here, from what I've learned, is how iPhone and Windows Mobile rate against these criteria.

---- Windows Mobile

  1. My access to your money: If you have a WM device, you probably have money. Even with carrier "discounts" they're not cheap. If you know what to get, it's worth the moolah, and you'll take advantage of what your chosen device has to offer by downloading apps that make use of it. This is as easy as:
    1. Trying to figure out where the big app stores are. There are a few, and they don't all support Windows Mobile, nor do they all have apps that will run on whatever version of WM you've got. It can be frustrating because Microsoft's practice of renaming products and slapping weird version numbers on things that are meaningless without context can easily leave you wondering what version of Windows Mobile you have (and wondering if what you've got is  the same as/compatible with PocketPC, WinCE, PPC, etc.).
    2. If not big stores, then searching the small independents where devs post their stuff on sites that look like they were made with a beta release of the first version of FrontPage.
    3. When you find an app, you go through whatever arbitrary transaction process the store/dev is using. This might mean creating an account with a site you'll never return to, handing your credit card info over to an independent whose trustworthiness is unknown, or even going through PayPal and then having to wait for the dev to check his email and manually respond with a serial number (or whatever).
    4. Run the app on your desktop which will kick off ActiveSync's install bits that install stuff on your PC in addition to the device.
    5. After clicking "Yes" or "I think so" or "Sure" on a few dialog boxes that pop up on the desktop and on the device, a CAB file is opened on the device and a local installer runs. This can mean more dialog boxes, and it can also mean having to make choices about things you don't understand (many users aren't going to comprehend the impact/difference between installing to the device's memory or to an expansion card).
    6. Run the app! Easy as 1-2-3-4-5-6!
  2. Uniformity of platform implementation: Unless things have changed, although the fundamental bits of the OS are the same, the configurations of Windows Mobile vary depending on the device. Some features might be stripped in favor of a smaller footprint for a device that's light on memory (why has it taken so bloody long for WM device makers to provide users more than, say, 128MB of storage space (without the user adding a memory card)?). Who knows what those features are. Even similar phones from the same manufacturer and carrier can vary enough that you can't rely on much beyond the expectation that there's some kind of phone hardware in place (some people still make calls with their phones).
  3. App distribution options and ease of install for the customer: As you may have figured out from my "Easy as 1-2-3-4-5-6!" list above, finding, buying, and installing apps on WM devices has always been a pain in the ass. Going back to my first PocketPC (the first iPaq (the 3630)), I wondered why I needed ActiveSync just to install some stupid little app. ActiveSync makes sense if, say, I'm syncing something with the desktop like mail or calendar data, but it doesn't make sense if I'm installing Super Solitaire 5000 Deluxe Color Edition. Where do you sell your app? How do you get the word out? I haven't looked into it for a while because it frustrated me so much in the past. I'm going to take a look again, and, because I plan to target one specific platform for my app, I also plan to develop for others. In the case of Windows Mobile, I'm hoping Microsoft copies Apple's model.

Speaking of which...

---- Apple's iPhone

  1. My access to your money: Apple's users tend to be enthusiasts. They blow money on stupid shit like knit cozies for their iPods and $3,000 earbuds that might sound great to a trained sound engineer, but which, compared to the buds that come in the box, sound no different to your sloppy unrefined auditory senses. If people are willing to pay for that, then they'll be begging to fork over dough for my app. It's a market of overeager zealots who will pay for things because they're new and different, but not necessarily because they're better (with most of Apple's own product-line excluded, as Apple's been doing beautiful stuff this century). People are still in the phase where, rather than buying iPhones to run their apps, they're buying apps to run their iPhones. It's gadgetophilia.
  2. Uniformity of platform implementation: You might have an iPod Touch. You might have an iPhone. You might have an iPhone 3G. You might have version 2.0 of the OS. Whatever it is, it's basically the same across devices. Different for the iPod, but the iPhone is quite sufficient. With the iPhone, you have a good idea of what you're getting, so you don't have to plan for as many oddities. Someone might have GPS, as with the 3G iPhone, or someone might have Apple's less precise, but still useable, location services that rely on cell and wifi information to determine your location. It's close enough for what I'm doing. As long as either of those things is present, we're good, and as I can count on those things being present, we're good.
  3. App distribution options and ease of install for the customer: Apple users have been bitching about using iTunes to install iPhone software. If they had any idea what it's like with other platforms, they'd shut it. While iTunes as an app store feels wrong and stupid and lame and stupid to me, at least iTunes is an app everybody has nowadays (aight - not everybody, but many, and that's good enough). Not that it matters much - with the introduction of Apple's App Store, you can browse apps on your phone, pay for, and install them without having to do some stupid syncing thing. You could be out at a bar where Jolene Blalock is hitting on you, and without having to run home to your iMac, you can buy, install, and run a crossword game before you've even had the chance to realize you've just made the biggest mistake in your life by ignoring her. And when you do realize it, and you see Jolene running off with another man, at least you'll have your crossword puzzles.

---- It's the Little Things

Microsoft is still so focused on the idea that the OS is what makes everything happen that they've let opportunity after opportunity pass by in the way of services.

In 1985, the relatively large amount of software you could buy for your IBM PC gave it a huge edge over technically superior platforms. It didn't matter so much that the disk in the box was the wrong size for your drive or that you needed a different video chipset - you could get those things, and if you were buying a game made by Origin, you did buy those things.

In 2008, if people have to work to get your bits onto their devices, you've screwed up. If they have to do the legwork themselves, figure out specs themselves, get around gotchas themselves, then you've screwed up.

Microsoft has been in the mobile space for a very, very long time. My introduction was, I think, eight years ago. In eight years, how much progress has been made in making it easy for the consumer to buy apps and install them? Not a whole lot. Yeah, there are ways for people to download apps directly to their devices, but that hasn't been the norm. Microsoft's own Windows Live app, which is great by the by, updates itself without going through the desktop, but it's not necessarily the case with other apps.

Apple has been at it for what feels like two weeks, and they've already taken on the problem of making it possible for people to buy and install apps even while driving. The solution is rough and needs work - you'll find plenty of bitching in the Apple magazines - but at least it's there, and you know Apple is going to refine it to the point that you'll wonder how buying apps on your device ever could've been done any other way.

There's plenty to whine about, and the princess-and-the-pea Apple crowd is doing a fabulous job, but with the iPhone where it is, there's no way Windows Mobile would be my first choice for a consumer app. Enterprise apps are a different story, but this post isn't about enterprise apps.

---- Microsoft Smudges Poop on Mona Lisa's Upper Lip

Whatever you anti-MS people say, Microsoft has done some brilliant work.

Of everything they've done, aside from Windows Mobile (which, despite my lack of interest for it as a consumer product, I love for many reasons), the Xbox 360 is at, or near, the top of the Microsoft heap.

Microsoft seems to be terrible at getting media companies to sign on for their services, but even with its small catalog of movies and TV shows, the Xbox Live Video Store rocks. There are some UI pains, but the experience is generally pleasant and makes me want to spend a lot of money.

That's where Microsoft made a mistake. That's where Microsoft smudged poop on the upper lip of its Mona Lisa (I'll explain what that means in a moment). There are other smudges, but we'll leave 'em for now. I only need this one as an example.

A couple nights ago, following a firmware update to my Apple wifi router, I was finally able to get my Xbox back online. For months it wouldn't connect. I stopped trying because I got tired of the letdown, but I was feeling unusually brave and resilient when I tried, and succeeded, to connect. It was awesome.

I went and browsed through the Video Store to see what had been added since the last time I'd been able to connect. Not much it turns out, but they have the new Stargate movie (Continuum) up there in HD, and that was enough to get me feverishly pressing buttons that I hoped would perform a transaction that would end with the movie being downloaded.

Unfortunately, I was too low on points (points are like funny-money that only work with Xbox Live). The obvious solution was to buy more points.

Typically, this is a fairly easy process. My credit card info is stored, so I don't have to reenter it. I just click a button to buy points, and then, after a brief video chat with some of Microsoft's lawyers who want to let me know how many years I'll go to jail should I abuse the point system, I get my points.

Between now and the last time I bought points, my credit card info was acquired by some very bad people in China who wanted to use it to buy things with my money. Modern tech being what it is, my bank's sophisticated Big Brother software noticed that, two minutes after paying for a latte on Hawthorne street in Portland, I tried to spend several thousand dollars on a sex slave in Beijing. They phoned immediately:

Bank: Mr. Blyth, our databanks show that you just purchased a latte in Portland and then tried to purchase a hooker on the other side of the planet shortly thereafter. The purchase got flagged as "Funny Business" in our system, and it's our duty to call you to get to the bottom of these shenanigans.

Me: Oh, well, I thank you for calling, sir, and, yes, these are shenanigans that I did not authorize. Please use your technology to stop these shenanigans.

Bank: Yes, sir. Can I put you on hold?

Me: I'd love it.

[Pretty music plays for thirty minutes.]

Bank: Hello, sir, are you still there?

Me: Yeppers.

Bank: All right. I just wanted to let you know that we've gone ahead and put a block on the payment for your latte. Is there anything else we can help you with today before I transfer you to Account Services to get you a new card?

Me: Thank you, no. I am very pleased with today's service. Please call me anytime.

I got my new card and then went about the tedious process of updating billing information for my car payments, insurance, and diaper service. Because Apple's router was being wonky at my Xbox, I didn't bother with Xbox Live at the time.

When trying to purchase those new points the other night, I finally got around to updating my billing info with the new card, but, by the end, rather than being excited to pay for videos, I was hoping to find a service through Xbox Live that would, in exchange for some of my points, electrocute me through the controller and put me out of my misery.

To begin, I couldn't find a simple "Buy You Some Lots of Points" button. There was a "How Do I Buys for Myself Lots of Points?" button, but all it did was take me to a screen that instructed me to return to the Xbox Live home and then, surprise!, buy some points. It really was that helpful. Since I'd gotten to this screen from the Xbox Live home (or somewhere near), the circular reference was unwelcome in my life, and I cursed out loud.

After much button slapping, I found that I could buy points once I'd navigated to the thing I wanted to buy. For the movie, that meant going to the Video Store, browsing the movies, selecting the one I wanted, and then clicking the "Add Points" button (or whatever it actually said). It was retarded. If MS wants my cash, they should make that the biggest button, and they should put it on every screen. They should build it into the Xbox controller itself. They should embed one in my forehead.

Making people search for a way to give you money is stupid. When you buy a pack of gum at the store, does the cashier argue with you? Do you have to walk through a hedge maze to get to the checkout? Are there a bunch of signs that say "Cashier This Way" that lead you in circles? When you get close, do they turn on the smoke machines, blindfold you, and spin you around?

No. And without various laws we have in place, they'd probably just shoot you on your way in to the store and then go through your pockets for change. Their goal, as is often the goal in business, is to take your money as quickly and as easily as they can, and in as great a quantity as possible for the least amount of work.

Buying points is metawork - it's the work you have to do to get your real work done. When I log on to Xbox Live, I don't do it because I want to spend my night trying to buy points. Buying points is not a game (if you work in the Xbox division, please print that phrase out and tack it on every wall of every hall and office in your building). It should be over with a push of a button. That's it.

It was an exceptional case since I had to put in new credit card information, but that was part two of the retarditity.

I don't have a USB keyboard, so I have to use the controller and the onscreen keyboard to enter text into the various fields of the credit card form.

Since this is still my account (RoryBlyth), you'd think it'd be a given that, though I have a new credit card number, all other things may very well be the same. Things like my name and address. But those things weren't automatically inserted for me. The form was blank, and I had to type everything out from the beginning.

It's a pain to enter in the credit card number and expiration date, but it's understandable. If MS already knew my credit card number, we'd have a problem.

But my name? And address?

How effing hard would it have been for Mister Lazy Stupid Coderpants to have taken that information from my account info and automatically populated the relevant fields with it? So what if there are minor details I might have to correct - my name doesn't appear on my credit card exactly as it does in my Xbox Live account info, but we're talking about the difference of a letter (one of my middle initials). I'd much rather go through the trouble of moving the cursor over to add two spaces and a letter to modify a populated field than have to type it all in from scratch.

Same with my address. It's the same damned address. Have you ever used an onscreen keyboard and console controller to type in your name and address? It's like trying to play Bach's cellos suites with your nipple on a gong.

Is it a legal problem? If so, just ask to access that info. It's not like there's a phobia at Microsoft about making users click "Yes", "No", or "Maybe So" eighty million times when they try to do something as simple as rename a file.

It's that kind of thinking - or lack of thinking - that smudges poop on Mona Lisa's upper lip. You're so close to something amazing, but you just had to go and smear feces on it.

I got a text a few days ago from a friend of mine who has a T-Mobile Dash. She had accidentally activated T9 input. The Dash has a thumb-keyboard, so T9 is a useless nuisance.

I have the same phone, albeit the unbranded version direct from HTC, and to shut off T9 I tinkered with the registry. This friend of mine, a "normal" user who knows nothing about tech, can't be expected to do the same thing.

I figured it'd be easy to turn it off, and that my difficulties were due more to owning the "raw" version of the phone rather than the one offered by T-Mobile. It's not as user-friendly. It's great if you're a dev, but you're probably better off going with the T-Mobile version if you, like my friend, just want to use the thing.

I googled for a solution, but all I found was frustration. It turns out this is a major flaw experienced by tons of users. There's no obvious way to turn T9 off. You can temporarily disable it for individual emails or texts, but the system reverts back to T9 when you're done. It's insane.

How could that have happened? It's such a fundamental thing. The rest of the phone is amazing, but the experience is seriously marred by this incredibly stupid oversight.

Like I said, it's the little things.

The iPhone isn't perfect. I think the complaints are a bit much and the result of people expecting perfection. Apple will continue to iron out the bugs. It'll be fine.

Imperfections aside, the iPhone is looking like a much better choice than a Windows Mobile phone for my app. I love the dev tools for WM, but that doesn't solve the problems I've detailed here.

Published Tuesday, September 16, 2008 6:34 PM by Rory

Filed Under: , ,

Comments

 

Mike said:

uh, no inclusion of Android in your analysis?  The first phone is going on pre-sale either September 17th or 23rd, and the phone will come out for the general public either September 23rd, October 1st or October 17th (I have these dates on very good authority BTW).  Not only that, it is being released by the 5th largest cell carrier in the US, in up to 23 markets!  How can you NOT include it????

Mike
September 16, 2008 7:55 PM
 

Paolo said:

Andriod pfft :)

I agree on all fronts, while our enterprise app is all windows/.net/microsoft to the core, when talking about building the mobile bits (web parts not included) it keeps coming back to just supporting the iphone and forgetting the rest.

My only question which I don't have a clear read on is - how do you sell an enterprise app in the app store which seems to be a general public repository for apps the general type public will use.  How do you sell an app to a specific audience - ie someone who is using our main application and want this as an add-on and this is a very niche market.
September 16, 2008 8:48 PM
 

Scott Williams said:

"Are there a bunch of signs that say "Cashier This Way" that lead you in circles?"

Never been in a Frye's Electronics huh?
September 16, 2008 9:34 PM
 

Kevin Daly said:

I broadly agree with you about this one.
Despite the laughable objections of the snotty-nosed CompSci Chalk Monitor sub-species of Apple fanboys (Smalltalk Onanists), I believe C# is a much better language than Objective-C...but your original description of the .NET Compact Framework as a wrapper around System.NotImplementedException still holds, sadly. The .NETCF team over the last few years have (barely) kept the languages in sync with the desktop, but there are still many key areas of the Compact Framework itself that are too skimpy (esp. System.Net and related bits), and they seem to have done *nothing* to facilitate programming against the mobile UI - which of course is where Apple creams Windows Mobile.

One small point - you don't actually have to use ActiveSync to install apps (I dropped that as a ridiculous over-elaboration a few years ago). Downloading and installing CAB files directly from the Net works just fine (I distribute software that way. Not for money, sadly. I probably could if I had the nerve of blissfully ignorant Alaskan moose-bothering women. Or whoever wrote the brilliant "I'm Rich" app. But I digress).

The App Store is a very good idea (and the value of having Apple take care of all the code signing nonsense should not be underrated), although there are *issues* in the implementation, in that inimitable We're-Apple-Therefore-Patronising-Arrogant-Bastards way. But overall it's an idea that I wish Microsoft would steal, and steal soon (although that said, they have a bad track record with their online commerce outings - they tend crappily to be restricted to North America, which is inexplicable for a company that overwise shows a good grasp of what it means to play in a global market)
September 17, 2008 1:30 AM
 

Xas said:

About the today's youth, it's very simple and I'll explain to you :
September 17, 2008 4:29 AM
 

Rory said:

Mike -

"uh, no inclusion of Android in your analysis?"

I'm not too excited about Android. That isn't to say I'm *not* excited about it - just not *too* excited.

I have a lot of experience with Windows Mobile, and I've been an Apple customer for many years. I know how to navigate the WM world to find the best devices, and I trust Apple. Even if the iPhone isn't where it could be, I trust they're going to get it there. And, it's already impressive as it is - what might happen over the next several years gets me going in a happy way.

Google doesn't have a track record here. When I think about Google, I think about search. I like some of the apps they've done - some are just brilliant - but I'm skeptical about their attempts to branch out from their core service. The further it gets from search, the more I wonder about what the outcome might be.

They might blow me away. I'm glad they've gone with their "Java-like" language. I'd much, much rather get to code against it with C#, but Java-like, to me, is better than anything native. Especially with a phone. The last thing I want is to make a small mistake that causes someone's phone to reboot every five minutes or bring it to a crawl. Managed is good.

I haven't looked at the APIs, so I don't know what's possible. From the OS's feature list, it looks like there's all kinds of stuff you can do, but it also looks like Android is going to come with the same problem as Windows Mobile: lack of uniformity.

The HTC Dream might kick ass. I love HTC. With the SMT5600, HTC permanently altered my view of mobile phones. Before that, I was using the same crap everybody else was - getting excited if I could get my phone to run hangman or a "magic eight-ball" game.

So, that's on Google's side. But it's an OS they're pushing - not a phone.

With the iPhone, I know what I'm getting - what customers have. Android *can*, for example, use accelerometers, but the device manufacturer doesn't have to include one. The same goes for many other features.

Apple tends to have tight product lines. Even with the diversity of iPod offerings nowadays, you're still not having to deal with a bunch of unknowns.

Those unknowns are where the Blue Screen of Death comes from (for the most part). Android, like Windows, is designed to be able to run on a wide range of hardware. Although you aren't (yet) going to have users slapping new CPUs, video chipsets, or whatever else in their phones the way they do with desktops, the device makers are still going to be putting things together in all kinds of ways.

Hardware configurations aside, we're also going to have manufacturers who just biff it. Think about some of the older Motorola Windows Mobile phones. Motorola cut corners and built devices below spec. The result was disastrous for them *and* Microsoft. It didn't wreck either company, but the people who had those phones were some uberly pissed off human-beings.

With an OS that can run in many environments, when something goes wrong it's hard to figure out where it failed. You can point fingers, but you'll run out of digits long before you can pin down the problem. The time required to troubleshoot might not be worth it. Your app could be perfectly written, but crash because someone built the phone with cheap memory to save two cents per device. When that happens, the consumer doesn't know why - they're going to default to the normal human behavior in these cases, and that's to attribute the problem to whatever preceded it. It's that "post hoc ergo propter hoc" thing - seeing causal relations where they don't exist. And you can't really blame 'em.

That means your company's reputation can be sullied because of something that was entirely not your fault.

Like everything else, Apple makes it easy. If you need someone to blame, you only need one finger (the "iFinger"?). Apple may not have built the components, but because of the way they operate, they're responsible. When Apple biffs, it might be because someone else's chip sucks, but they control the entire software and hardware stack.

For Apple, cutting manufacturing costs at the expense of hardware quality, although an option, would be insane. Not to say they haven't screwed up - things happen. The stuff is also boutique-ish, so there are some problems you can expect to find across a product line. But, again, you know who to blame, and you can expect Apple to respond.

Because this app of mine needs, at least for the full version, GPS, a net connection, blah blah blah, I need to be able to count on the hardware being present - and *working*.

There's so much to think about when doing consumer software - Apple has done away with many of the obstacles directly (the App Store, etc.) and indirectly (uniformity of hardware, etc.).

We'll see dominant hardware platforms emerge for Android, but they're going to be constantly shifting based on fashion, business vs. consumer needs, etc. - so many unknowns and moving targets.

That's the story for Windows Mobile - do you need/want a keyboard? Wifi? GPS? Square or rectangle screen? Do you want a "pretty" phone? A rugged phone?

You don't know what's out there. Windows Mobile is so amazingly flexible that you can't count on much. It's great for business. If you need a device that's fast, has a lot of storage, a big high-res screen, a "large" keyboard, superior battery life, and the bits for running your in-house enterprise app, you can find it. It's out there somewhere. Even if you can't find exactly what you want, you'll likely find something very, very close. And you know you'll have SQL Server, web services, Exchange support, and other bits to code against.

As a dev, I'd rather go with Windows Mobile. As I stated in the post, I love Microsoft's dev tools. I love .Net, I love C#, I love SQL Server Mobile (or whatever they're calling it this month)...

But the app is for consumers. I have to develop it with that in mind. The big compromise here, then, is Apple's dev tools. I don't like 'em, and that's all there is to it, but I'll have to use them.

I guess you could say that my lack of interest in Android for this app is similar to my lack of interest in WM. I love WM, and I might wind up loving Android, but they're both at a disadvantage when it comes to consumer apps.
September 17, 2008 3:14 PM
 

Rory said:

Paolo -

"My only question which I don't have a clear read on is - how do you sell an enterprise app in the app store which seems to be a general public repository for apps the general type public will use."

Hm... why would you want to sell your enterprise app on the App Store?

I haven't thought about it yet, but I also haven't thought about the iPhone as a business platform. I've read a little from people who're planning to use it, but I haven't read much about *how* they'd do it.

I've seen ads in the back of a couple Mac magazines for consultancies that will build enterprise iPhone apps, but, again, I haven't looked into the details.

The more I think about it, the more I wonder if it makes sense. Even if you could package the app and sell it that way, you'd almost certainly have to customize it for each company's infrastructure. Firewalls, databases, mystery platforms on the back end...

Getting curious. Hadn't thought much about the Hows and Whys of the iPhone as anything but a consumer platform.

Interesting...

"How do you sell an app to a specific audience - ie someone who is using our main application and want this as an add-on and this is a very niche market."

Yeah. Dunno. That's the biggest concern I have.

The App Store as I've seen it reminds me of Xbox Live. As long as the offerings are limited, it works well. But when you get more than a few dozen videos or shows or games listed on Xbox Live, it turns into a pain in the ass. You have to page through so much crap you have no interest in. There are *some* categories, but it's just not done well enough to handle much more than it already is.

Apple is going to have to develop some very clever ways of getting App Store products in front of people without overwhelming them (I'm talking about shopping *on* the iPhone). They've got some of this going on already - it's always good to separate the most popular apps from the rest - but when there are more and more apps, and when so many are extremely popular, what's going to be the best way to catalog them?

Screen space is limited, and different people will have very different shopping preferences. I like as much detail as possible - I want ratings, reviews, feature lists, screenshots, demos, and more, but I also want to be able to access that stuff easily. With a device, it's tough to get more than the app's icon, title, and one or two other bits wedged in before running out of room.

We'll see. As I said earlier, I trust Apple will get it all figured out, and I look forward to seeing how they do it :)
September 17, 2008 3:28 PM
 

Rory said:

Scott -

"'Are there a bunch of signs that say "Cashier This Way" that lead you in circles?'

Never been in a Frye's Electronics huh?"

That's different.

By confusing you with signs instead of costly employees, they pass the savings on to you, the customer.
September 17, 2008 3:30 PM
 

Rory said:

Kevin -

"Despite the laughable objections of the snotty-nosed CompSci Chalk Monitor sub-species of Apple fanboys (Smalltalk Onanists)"

What a great summary :)

"I believe C# is a much better language than Objective-C...but your original description of the .NET Compact Framework as a wrapper around System.NotImplementedException still holds, sadly."

I'd completely forgotten I said that.

That's genius. I'm totally high-fiving myself right now.

"One small point - you don't actually have to use ActiveSync to install apps (I dropped that as a ridiculous over-elaboration a few years ago). Downloading and installing CAB files directly from the Net works just fine"

Yeah - I mentioned that in the post. As usual, though, it's easy to miss details like that, as I tend to go on quite a bit (see previous comments for this post).

The example I used was Windows Live for Windows Mobile. It works demmed well - to the point that it's a no-brains-required operation.

That said, installing from CABs has almost the opposite problem from going through ActiveSync. Where you and I are clearly forward-thinking tech luminaries for thinking that ActiveSync is just a touch much, CABs are just a little *too* stripped down.

I'm a nerd, and a Windows Mobile nerd at that, so I (usually) know what's going on. After a CAB runs, I expect to be able to go to my apps, find the installed thingy, and run it. But a regular user might not make that connection.

Also, this gets us back to distribution. Downloading CABs *works*, but it's not a well known way of distributing WM apps. Plus, there's the issue of having to find the apps in the first place. Pocket IE is a fabulous browser, but I still wouldn't want to use it to hunt down software for my phone. That'd mean googling, finding, and reading - all on that little screen with my measly Edge network connection.

Like other Windows Mobile goodness, that's dandy for enterprise apps, but a hindrance to consumers.

"The App Store is a very good idea (and the value of having Apple take care of all the code signing nonsense should not be underrated), although there are *issues* in the implementation, in that inimitable We're-Apple-Therefore-Patronising-Arrogant-Bastards way."

Yeah, huh. I've been reading about the process - about the mystery behind Apple's choices (what will/won't make it into the App Store) - about how Apple puts a stop to anything that remotely competes with its own software.

The no-competition aspect sucks dog balls, but it also makes sense. The Windows freeware/shareware/regular-ware market shows what happens when anybody can develop and sell an app. You wind up with dozens of apps competing in the exact same space, and perhaps only one or two are any good, but you wont know it until you've paid for, run, and gotten frustrated by one.

By tightly controlling what's allowed, Apple gets to exercise some quality control over the third-party software market. They also get to protect users from wonky apps. Security, too, is an issue - especially with mobile phones. The last thing you want is some self-propagating spammer tool that turns your iPhone into a relay for v14gr4 emails.

I'm not saying Apple has done well. There's a lot of anger out there right now over how it's been going. Crappy as that is, I'm optimistic that Apple will come up with a solution that satisfies their interests as well as those of third-party devs, though I'm also realistic and expect limitations that'll continue to give Apple what might be perceived as an unfair advantage.

In developing a consumer app, I *want* that kind of control. I don't want to write something that five people will find, pay for, love, and then miss when I can no longer afford to keep the project going.

I want that, however, only if *my* app is one of the selected :)

The carrier also has a lot to lose if apps go wrong. AT&T claims that the limitations are all Apple, but that's just spin. Apple controls the SDK, and in doing so limits what devs can do. Those restrictions protect the phone (to an extent), and that saves AT&T from customer support nightmares that ought to be easily avoided. Plus, AT&T doesn't want to be known as the carrier that brought us the infrastructure that made iPhone viruses possible :)

So, because AT&T's concerns are likely taken care of by a subset of the iPhone SDK's limited functionality, the rest being from Apple, they can point the finger Appleward. It all goes back to Apple...

...and that patronizing arrogance you mentioned.

Hopefully it'll get better.

"But overall it's an idea that I wish Microsoft would steal, and steal soon (although that said, they have a bad track record with their online commerce outings - they tend crappily to be restricted to North America, which is inexplicable for a company that overwise shows a good grasp of what it means to play in a global market)"

I don't get it either.

From all the me-too services (Soapbox being a miserable failure of an example), and all the times MS has produced third-rate copies of those other services, you'd think they'd figure it out and just license the technology. Provide an MSN front-end, but put someone else's search engine behind it.

Awesome. I just did a search for Soapbox to see what happened to it. Found MSN Video, but wasn't able to access it because my browser and OS aren't supported.

Maybe that's it - as I was saying in the post, MS is still way too OS-focused, thinking the future will be determined by the desktop.

I'm not one of these I-want-the-net-as-an-OS people - I like having my big bloated software, and I like OS X - but I'm also not stupid. I spend most of my time on the net. Very little is spent running software locally, but what I do run locally, I run locally because the experience can't yet be duplicated online.

Other than that... it's online, and MS has consistently blown it here. It's a cliche going back for years, and it's sad that it's still going - the Microsoft-misses-the-online-boat cliche.

What was the deal with Soapbox? Trying to get people to run IE on Windows. Silverlight - Windows Media - that's what they're pushing, and that is *sooooooooooo stupid*. It might have worked in 1998, but it's an effing disaster in 2008.

How much money was dumped into Soapbox? How much came back? And who in the hell thought it was a good idea?

Let's make a YouTube clone that isn't really a clone, has retarded system requirements, and, except for what really is outstanding video quality, basically sucks!

Sign me up.

Not that licensing Apple's tech for Windows Mobile is an option here. But there has to be *some* kind of a good solution that doesn't involve retard branding, constant name-changing, exclusive-to-the-point-of-unusable system requirements, and so on.

We'll see.

We'll see...
September 17, 2008 4:38 PM
 

xtine said:

I'm sure that turning off T9 would have been as easy as flipping through the 5,000 page manual that came with my Dash, but I was at work and I panicked.  And thanks to The Smartest Man in the World, Texting for Retards is no more on my beloved precious phone.
Thank you, Rory.
September 17, 2008 9:23 PM
 

Cliff said:

Solidarity bro...

I couldn't not disagree with you more. (Sorry 'bout that dbl negative... been trying to write/comprehend/experiment w/ ObjC and the dbl negative thing just sticks after writing code.) Your points on Andriod, the Apple store, everything is on point. I would add that just because you're using managed memory doesn't protect you from making that simple mistake that sends the phone in a constant reboot cycle. I've seen this happen on Blackberry devices just because the wrong version of the compiler was used.

BB griping aside, I believe Microsoft could finally make a dent if it did the opposite of its exclusivity practices, what it's known for doing so well. Instead of trying to clone somebody else's gem and lock it down to a Windows only stack offering only minor if any advatnages they should embrace variation. What if MS made some sort of widget/gadget/fidget that runs flawlessly on OS X that integrated your WM phone or some other MS technology? What if they stood behind it? Supported it? I recently tried to get my wife to use a Mac Pro instead of our dinky 4 yr old WinXP desktop and the whole idea fell apart because she can't synch her AT&T Tilt to the Appl Mail/AddressBook! I then explained how I could drag drop my songs/picture fro my Blackberry easily after just plugging it in to either a Mac or a Linux box without needing to install Active Synch or anything. It would seem intuitive that supporting Apple as an accepted device for a WM phone would sell less Windows machines. But if you attended at least one course in economics, checkbook balancing, or even basic statisics you could figure out that opening your product to a competing platform would sell more copies of your product than it would take away customers of your competing platform. Do they really think that opening WM 6 to OS X would cause all existing Windows users to buy a Mac? If anything it would increase the market share they have in mobile to those Mac zealots who are smart enough to know a touch screen isn't the productive thing in the world. Anyway this is spoken at literally the eleventh hour after two Bud Ices and a Coors Extra Gold so it might sound insane in the morning.
September 21, 2008 8:17 PM
 

The Cowboy said:

You know, of course that I'm dying to know what Rory's "killer app" is.  

Personally I think you're right, for the end consumer iPhone is going to have a greater reach, but I'm such a .Net crackhead I would probably do it in C# for WM anyway.

Then again, WM really is still a wrapper around System.NotImplementedException, as I've found myself searching for code to implement things like BackgroundWorker.  Luckily OpenNetCF has taken care of a lot of the shortcomings, but dammit I want a stack trace!
September 21, 2008 11:10 PM
 

Celes said:

My phone plan is up towards the end of December, and now that I'm not so dirt poor anymore, it's time to get my first 'not free with with plan' phone.

Every now and then I've been swayed one way or the other by which phone and which carrier, but right now I think I'm in 'no idea land'.

It sounds like a lot of the developer and consumer concerns are the same. For me, I there is one more obvious one- I am not a "Omg, my new pink mac laptop for tons of $$$" person. I don't want to pay a ton of money each month and for extras- I can't really afford it.

I also run Windows. I don't have Itunes installed and don't want it. Windows ports of Mac software leave much to be desired. Maybe I'm stubborn, but I also kinda want a Windows solution.

I am not so stubborn that I will not go with whatever will rock my casbah the most without making me hate it for the money it's costing.

I have a few months to think about it.
September 22, 2008 12:09 PM
 

Petar said:

hey Rory, you may want to know that T9 creators (Tegic/Nuance) have got a killer application called T9 Nav. It can also be used to ease the search for operator-provided applications (that are available for download). A really neat solution.
September 22, 2008 3:38 PM
 

Chris said:

It sounds like you want to make something similar to the "I am rich" app that was sold in the iPhone store.

"Apple is going to have to develop some very clever ways of getting App Store products in front of people without overwhelming them (I'm talking about shopping *on* the iPhone)."

The last iTunes update has the iTunes genius. Maybe they will make an appstore genius as well to recommend titles based on your past purchases. I see that coming in the near future.

BTW, I really like my work now. I guess it turned out ok.
September 22, 2008 7:58 PM
 

Rob Miles said:

When you were asking about ways to make wads of cash some time back I nearly put a post up saying you should crank out some iPhone applications. As a Windows Mobile Geek who has had one of Apple's toys for a year now I heartily endorse your remarks about WM vs iPhone.  I reckon that you are right on the money with all your comments, particularly the ones about getting paid for your software. If you want some more ideas for an iPhone device I've got a couple lying around if you are stuck (as if).

The only thing that is stopping me from having a go is lack of time and a nervousness about learning Objective C and  a new way of doing things. The deployment story when you get started with iPhone looks a bit scary too, with talk of certificates and whatnot before you can run a program on the device. Visual Studio really spoils us in that respect (although lately you are a bit at the whim of your carrier) unfortunately.

My advice would be to go for it. And don't rule out enterprise stuff either. People are having to bend their corporate systems to accommodate all the iPhone owning managers who want to use their shiny new toys. There are a lot of people out there who want to do company business on an iPhone.

I'm *really* looking forward to Windows Mobile 7. A device as easy to use as an iPhone, which I can program in C# using Visual Studio would be pretty much nirvana for me, especially if Microsoft come up with an app store to go with it.
September 23, 2008 7:37 AM
 

Tony Zielinski said:

Yo Row Ree! Android looks cool based on what little screencasts are out there.  I think iPhone is your target market Rory.  iPhone is currently lacking much needed apps that have been available on WM for ages, namely a turn-by-turn GPS app.  Why hasn't anyone released one yet for iPhone!  I just bought a Garmin for the very reason that my WM phone was stolen and my iPhone does not have a directions app with speech directions, or even that doesn't require the user to click 'next'!  This is unacceptable, Rory, and I'm leaving it up to you to save us from this tragedy.

Also, I spotted you on Hawthorne, you hippie! :P
September 23, 2008 11:23 AM
 

Rob Miles said:

I think the reason that there is no turn based GPS is that Apple aren't that keen on one in the app store. Either they are nervous about something that might break if you lose network coverage or they have plans to put their own into the phone at some stage. Either way, I think trying to put a proper navigation app out there is a no no.

The same goes for music playing apps. I had some nice ideas for really clever, context sensitive, music playing stuff but I don't think Apple want anything that might compete with the built in player.
September 24, 2008 1:31 AM
 

John R Woodward said:

Build your app. I bought an IPhone 3G six weeks ago and before that, the last time I touched an Apple product was roughly 1981 when I briefly had a job demonstrating software in a bookstore that had branched out into systems and software. Been a DOS/Windows user since 1982, but I am so disgusted with VISTA and MS's political activism that I am trading up to a Linux desktop and will be using the IPhone until my stepkids murder me to pry it out of my cold, dead hands. I know nothing of the IPhone dev tools, but it occurs to me that you could minimize your involvement with IPhone OS if you just ran your app in the Safari browser and got it to query the GPS briefly behind the scenes. Is that possible? Doesn't Safari by default exchange info with the GPS? I can transfer address data from a website to the GPS with a tap -- that's a default ability my phone has. Would this process be accessible in the SDK tools?
Gotta go. One of my stepkids is reaching for my IPhone and she's got a chef's knife in her other hand.
September 24, 2008 11:36 AM
 

Nikita Polyakov said:

Awesome post! Been a while since I followed your posts.

I've been screaming at WM for years "It's just software, fix it quick, before 'they'[customers] come."

Well the consumers came, and lucky people will get HTC Diamonds for XMas this year and all.

But damn, fix the damn software.

At least HTC took matters in their own hands and delivered kick ass home screen that does not scare consumers and Sony is working on some "Widget Store" for their Xperia "home slices".
Dunno why HTC does not bake in a App Store of their own and steal the show...

[BTW, trying to convert from ASP.NET MVP to Mobile MVP this year.
I've only been speaking at CodeCamps about WM Dev for few years now...]

In reply to your post - WM does has a few prominent software "houses" that sell just about everything you might need and don't have to deal with JoeSoftwareInc., places like Handago and like are doing well.

But does the consumer know about them? No!

Why?
Because TMobile or AT&T have their own app stores, which they call something else on the home screen of pocket IE, selling great things like "our own expensive GPS navigator software" and "games you really don't want" and ringtones. Just $4/m an app or something.

Btw check out SkyFire.com if you have WM phone laying around.
It works on my blackjack, a phone has half the screen of iPhone and I can do more online they iPhone ever can with SkyFire app.

Either way, you are correct, "we" need WM App Store.

I prefer it to be as cool as Zune 3.0 on-device downloads store for 'music and stuff', pretty please Microsoft Mobile Team.

While they are at it, Zune 3.0+ software on my WM phone please. Like yesterday. So I can finally enjoy a Zune experience in my car, though bluetooth  connection.

I digress.

I think we are thinking about building the same app...we should talk. Or not. But what you described lives closely to what I have been frustrated by that is NOT there in the Mobile space now, that uses all these things and make lives better.*

*by better I am referring to my "F*CK" moments during a regular day, when I wanna do something somewhat simple and my devices and systems, while perfectly capable, have no software that does those things for me. And things like that have many ways to be monetized. So "I have a Dream..." vision for this app is in my head and I suspect you have something similar in mind.
September 24, 2008 3:46 PM
 

Lloyd said:

Starting to hate Outlook. Never updates your feed.

If iPhone seems the logical choice, go for it :) Looking forward to chatting on XBL. I don't really have much of an opinion on the hardware issue, but I don't think I'd ever spend $600 on lingerie for my gf unless she was /really/ hot and I was rolling in money.

Not calling my gf not hot... whistle

Lets hope she never reads this :P

Any podcasts coming zoon? I have my Zune now and I've got askaninja for now.. but I need some roryness in my life, weekly! :P
September 27, 2008 4:20 PM
 

Dare Obasanjo aka Carnage4Life said:

September 28, 2008 1:52 PM
 

Bagel Belly Blog said:

I can't figure out how to reinstate my Delicious links since upgrading to MovableType 4 (something to do with Action Streams? Lazyweb?), so here's a bunch of links by hand: Don't Alienate Developers iPhone vs. Windows Mobile - Apple...
October 5, 2008 2:45 AM
 

Android strategy « Smurf on Spreadsheets said:

October 7, 2008 5:34 PM
 

Kris said:

I had the same problem trying to buy points on the 360. I thought I was just stupid... glad to hear I'm not the only one.
November 6, 2008 1:40 PM
 

Yannick said:

I am a MS shop, live bye it, if it closes, i'll be selling flowers...
BUT I got an Iphone and it Rocks !

What's your app, I must need to pay 5$ for it ! Soon ;-)
November 7, 2008 10:17 PM
New Comments to this post are disabled

About Rory

I *own* this site, you loser.