Tag Archives: apple

apple, development, professional, software development

Apple iPad ascendant in business computing

1 Comment

Think Apple’s iPad is a consumer platform? Think again. I’m at the Cloudforce conference in London; and the level of iPad visibility has been striking. I’m not talking about attendees clutching the devices, though there are some. Rather, it’s the number of mentions and actual usage examples that are in the presentations. Before the keynote, Peter Coffee from Salesforce.com was using an iPad for interview notes, using it like a pad of paper. Next, we had demos of Salesforce.com’s new Chatter for mobile running on the iPad. Next, a representative from case study Bausch+Lomb mentioned that his company has just deployed 700 iPads to its sales force.

image

All business use cases, and all the more impressive given that they are incidental to the theme of the event.

Personally I have mixed feelings about this development. I’ve been a fan of the tablet format for years; here’s an article from 2003 (with apologies for the dated layout) in which I enthuse about an early Acer tablet. Some of the features for which the iPad is praised, like the ease of sharing what’s on the screen with others, are things I’ve long taken advantage of with Windows tablets.

The iPad is succeeding where Windows tablets mostly failed, thanks to its better design, lighter weight, longer battery life, and lower price. That’s welcome to me since I like the format, but the locked-in nature of the platform alarms me. Apple to be the single pipe for all public software deployments? No Flash, Silverlight, Java, or any runtime or other enabling software which Apple chooses not to approve?

This is merely an observation though – what counts is that users are adopting the device and enjoying what it offers them, in business as well as for personal use.

Now that Apple has shown how to make the tablet concept work, others are climbing on board, mostly with Android devices. The next point of interest is whether these also succeed; and even whether Microsoft can clamber back into the market either with a new wave of Windows devices, or more plausibly with the Windows Phone 7 OS (though the company claims not to be contemplating this).

For the moment though, broad reach deployment must include either an HTML version of your app, or native iOS.

google, internet, security, Web

Anti-virus software continues to fail

2 Comments

I received an email from Trusteer noting that anti-virus detection rates for the latest Zeus variant are very low. This analysis shows that at the time of writing only Panda, among the major anti-virus products, picks it up. Does this mean we should all switch to Panda? No, because next time it will be one of the others that works, or none of them will work. You can only sympathise with users who imagine they are protected from malware because they have security software installed which tells them so.

The solution? Well, white-listing, visiting only trusted web sites, not opening attachments, keeping your OS fully patched, and so on. None of them perfect.

Alternatively, a new model of computing. One of the attractions of locked-in platforms like Apple’s iPhone and iPad is that they are harder to infect. Google’s forthcoming Chrome OS is even better designed from a security perspective. I am surprised that this aspect of cloud+device computing does not get more attention.

apple, iphone

Ten reasons the Apple iPhone 4 beats the Android HTC Desire

7 Comments

I’ve recently been trying the Android-based HTC Desire for some development research. I’ve also been using the iPhone 4 since its release in the UK. How do they compare? Yesterday I posted Ten ways the Android HTC Desire beats Apple’s iPhone. Now here’s the opposite – ten ways the iPhone is better. Conclusions then? Maybe in another post.

1. The iPhone gets left alone by the operators, presumably at Apple’s insistence. When the OS is updated, everyone gets it at around the same time and from the same source – Apple. Contrast this with Desire, the software for which is customised by each OEM with different apps and possibly some bits missing. Orange UK removes Google Talk, for example. Right now everyone wants Android 2.2 “Froyo”, but whether you have it or not depends on which operator you are with and/or whether you are willing to hack your phone a little to remove the branding.

2. The iPhone is more beautiful. The Desire is not bad, but purely as a design object does not come close to the iPhone with its smooth lines and solid, cool metal and glass construction.

3. The iPhone is a better music player. Not surprising given that it evolved from the iPod family of devices. iPod for iPhone is delightful to navigate, does videos and audiobooks, and integrates with iTunes for buying songs over the air. Now, you could always install Amazon MP3 for Android to enable OTA music download, whereas – no surprise – this is not available for iPhone. The speaker is better on the iPhone, not that you are likely to use it much for music.

4. The battery life is better. My Desire is only a month old, but I struggle to get a full day out of it if it is used with any intensity for wi-fi, 3G internet, web browsing and so on. The iPhone normally makes it. Neither is great of course – there are simpler phones that last for a week, though they do much less. The Desire’s battery problems are mitigated by the ability to carry a spare, though given the way the back case clips on I suspect it might break if frequently removed and refitted.

5. The iPhone has better text input. It is not too bad on the Desire, bearing in mind that it is a touch device only, but the iPhone has that great press-and-hold edit bubble that lets you move the cursor (though the Desire has the optical joystick which also works for this). Another iPhone advantage is that if you touch the wrong letter, you can slide to the correct one, whereas the Desire keyboard uses this gesture to enabled accented characters and so on, which is less useful for me.

That said, the iPhone has its annoyances. Here’s one that drives me nuts. There must be a lot of people at Apple called Tom, because whenever I type my first name it wants to correct it:

image

At this point, if I hit return I get Tom. If I hit spacebar, I get Tom. In order to keep what I have actually typed, I have to tap the word Tom, which is counter-intuitive as it feels like selecting it, then it goes away. Having mentioned it here, I am sure someone will point out a way to fix it; please do.

6. App availability is better on the iPhone and the quality is better. I say this with reluctance, because the iPhone App Store is also full of rubbish, but overall I find the standard slightly higher. This is actually logical: the Apple App Store has a higher barrier to entry, both financial and in terms of developer skills. In addition, the App Store is nicer to use than the Market, and works better. In my case I had to open a port on my firewall before I could download from the Market at all.

7. The iPhone scores on “it just works”, with greater UI consistency and a sense that Apple has thought about all the common actions on a smartphone and made them work well. Often the iPhone goes one better and makes everyday apps fun to use. The messaging app on the iPhone, for example, is attractive as well as functional. The Desire equivalent is effective, but dull. The single main button on the iPhone makes it quick to learn, whereas the Desire’s five buttons (Home, Menu, Trackpad, Back and Search) give you more to think about, and mean more frequent switching between touching the screen and clicking a button. The Desire is missing some basic things out of the box, like a notes app, though you can add one for free from the Market.

If money and freedom are no object, I’d suggest iPhone over Desire for someone who wants to get on with their work and not tinker with their phone.

8. The iPhone has a better screen. 960 x 640 vs 800 x 480, and is a little better in sunlight than the Desire.

9. I prefer the Exchange app on the iPhone. For example, I use a lot of folders, and the iPhone shows me these on the main screen. On the Desire, I have to click Menu, then Folders, then select a folder from the pop-up window.

10. The iPhone has smooth, attractive transitions between screens. For example, if I am on the home screen and tap Mail, I get a nice zoom animation. On the Desire, screens typically just appear, or there is some lag and brief ugliness. It all contributes to a smooth-as-silk impression operating the iPhone, whereas Android feels rough and ready by contrast.

All these things are relative. Next to my old Windows Mobile 6.0 phone, Desire is delightfully smooth.

apple, google, iphone, mobile

Ten ways the Android HTC Desire beats Apple’s iPhone

6 Comments

I’m just getting started with Android development, for which I got hold of an HTC Desire. And I’ve been using Apple’s iPhone 4 since its release in the UK. So which is better? There’s no satisfactory quick answer to that, though the two phones are certainly comparable; perhaps too much so, judging by Apple’s lawsuit. I thought it would be fun though to do a quick couple of posts on how they compare, of which this is the first. Reasons to prefer iPhone coming next. The following points are based on the Desire running Android 2.2 “Froyo”.

1. You can plug in a micro SD card to expand the storage. Apple does not support this with the iPhone; it may be because it wants to control what goes on the device, or because it uses storage space as means of selling more expensive versions of its devices.

2. Related to (1), you can copy a file to the phone by attaching it to a PC and using the filesystem. To do this with the iPhone you need additional software, or a solution like Dropbox which copies your document up to the Internet then down onto the iPhone.

3. You don’t need to install iTunes to get full use of the device. Some like iTunes, some do not; it is better on the Mac than on Windows, but it is great to avoid that dependency.

4. You can share your internet connection without fuss, either by creating a portable wi-fi hotspot, or through a USB connection.

image

5. Adobe Flash works on Desire. Coming soon is Adobe AIR, which will enable developers to create Flash applications as well as Flash-driven web content.

6. The platform is more open. Developer registration is only $25.00 (vs $99 for iPhone) and there are fewer restrictions concerning how you develop your application, what sort of app you create, or what language you use. The standard language is Java, which is easier to learn and more widely used than Apple’s Objective C.

7. The Desire has instant screen switching. Press home when already on the home screen, and you get thumbnails of all seven screens; touch a thumbnail to bring it to the front. Widget support means you can put those screens to good use too – not just for storing app shortcuts.

8. The battery is removable. The obvious advantage is that you can carry a spare with you.

9. It uses a standard USB cable. A small point perhaps; but it is easy to lose your cable or not have it with you, and being able to use a standard cable is convenient.

10. There’s no issue with the antenna when using the Desire without a case.

apple, flash, iphone

Samsung Galaxy Tab – among the first of many iPad clones

4 Comments

Samsung has announced final details and specifications of the Galaxy Tab, a tablet device running Android 2.2 “Froyo”.

image

It has a 7-inch1024x600 multi-touch screen, 1.00 Ghz processor, GPS, wi-fi, 3G internet, 1.4 megapixel webcam, 7 hours battery life if playing a video (I imagine much longer than that in normal use) and 16GB or 32GB RAM plus optional MicroSD.

Apple’s iPad has a 9.7-inch 1024 x 768 screen and better battery life – 10 hrs while playing a video, according to the specs.

So why would you buy a Galaxy Tab? Well, it is smaller and therefore handier, though you will squint a bit more. It has some freedoms that the iPad lacks, such as Adobe Flash, MicroSD, and FLAC playback. It has a camera. You will not need iTunes in order to interoperate with a PC.

I imagine the main reason, though, is that the Galaxy Tab will be cheaper – even though I cannot find prices anywhere, it is inevitable. This and other would-be iPads will be positioned as cheaper alternatives.

This will not harm Apple at all. It likes to occupy the premium ground and does so with great profitability.

But could the Galaxy Tab be better than an iPad? Well, it will be for certain tasks where the iPad is lacking – see above – but it will lack the careful design and attention to detail which characterises Apple’s device, and of course will not be compatible with all those iPad apps – though in some cases there will be Android equivalents.

Further, all the same doubts which were expressed about the iPad before its launch apply here as well. Do you really want a smartphone and a tablet and a notebook, and if not, which one will you abandon? Is it worth yet another contract with a mobile provider just to keep your tablet connected? It is possible that although Apple can make this category work, others will struggle.

When I played briefly with a Dell Streak, a 5-inch Android tablet, I found myself thinking that it will be a good deal when they sell them off cheap. Without that incentive, it is too big for a phone, too small for much else other than watching videos on the plane.

I would like to try one of these devices, of course, but whether they will succeed is an open question.

apple, iphone, mobile, software development

Review: Tapworthy – designing great iPhone Apps by Josh Clark

Developing for iPhone is a hot topic. Many developers are not only having to learn Apple’s Objective C and the Cocoa application framework, but are also new to mobile development. It is a big shift. Josh Clark is a iPhone designer, and his book Tapworthy is about how to design apps that people will enjoy using. It is not a programming book; there is not a single snippet of Objective C in it.

His book illustrates the power shift that has taken place in computing. In the early days, it was the developer’s task to make an application that worked, and the user’s task to understand how to use it, through manuals, training courses, or whatever it took.

There are still traces of this approach in the software industry, but when it comes to iPhone apps it has reversed completely. The app creator has to build an app that the user will find intuitive, useful and fun; otherwise – no sale.

An early heading reads “Bored, Fickle and Disloyal”. That’s the target user for your app.

Clark’s point is valid, and he does hammer it home page after page. You will get the message; but it can get tiresome. His style is frank and conversational: some readers will love it, others will find it grating after a chapter or two.

Even if you are one of the latter group, it is worth persevering, because there is a ton of good content here. There are also numerous short interviews with developers of actual apps, many of them well-known, discussing the issues they faced. The persistent issue: we’ve got a complex app, a small screen, and intolerant users, how on earth do we make this seem simple and intuitive?

Constraints like these can actually improve applications. We saw this on the web, as the enforced statelessness and page model of web applications forced developers to simplify the user interface. It is the same with mobile. Joe Hewitt, author of the first generations of Facebook for iPhone:

There is so much stuff that is actually better on the small screen because it requires designers to focus on what’s really important.

So what’s in the book? After a couple of scene-setting chapters, Clark drills down into how to design for a tiny touchscreen. Be a scroll sceptic, he says. Chapter 4 then looks at app structure and navigation. Chapter 5 takes you blow by blow through the iPhone controls and visual elements. Then we get a chapter on making your app distinctive, a chapter on the all-important start-up sequence and how to make seem instantaneous, and a chapter on touch gestures.

The last three chapters cover portrait to landscape flipping, alerts, and finally inter-app communication and integration.

Throughout the book is illustrated in full colour, and the book itself is a pleasure to read with high quality paper and typography. 300 pages that will probably improve your app design and increase its sales; a bargain.

 

.net, development, microsoft, professional, silverlight, software development, visual studio, web authoring

Visual Studio LightSwitch – model-driven architecture for the mainstream?

2 Comments

I had a chat with Jay Schmelzer and  Doug Seven from the Visual Studio LightSwitch team. I asked about the release date – no news yet.

What else? Well, Schmelzer and Seven had read my earlier blog post so we discussed some of the things I speculated about. Windows Phone 7? Won’t be in the first release, they said, but maybe later.

What about generating other application types from the same model? Doug Seven comments:

The way we’ve architected LightSwitch does not preclude us from making changes .. it’s not currently on the plan to have different output formats, but if demand were high it’s feasible in the future.

I find this interesting, particularly given that the future of the business client is not clear right now. The popularity of Apple’s iPad and iPhone is a real and increasing deployment problem, for example. No Flash, no Silverlight, no Java, only HTML or native apps. The idea of simply selecting a different output format is compelling, especially when you put it together with the fast JIT-compiled JavaScript in modern web browsers. Of course support for multiple targets has long been the goal of model-driven architecture (remember PIM,PSM and PDM?) ; but in practice the concept of a cross-platform runtime has proved more workable.

There’s no sign of this in the product yet though, so it is idle speculation. There is another possible approach though, which is to build a LightSwitch application, and then build an alternative client, say in ASP.NET, that uses the same WCF RIA Services. Since Visual Studio is extensible, it will be fun to see if add-ins appear that exploit these possibilities.

I also asked about Mac support. It was as I expected – the team is firmly Windows-centric, despite Silverlight’s cross-platform capability. Schmelzer was under the impression that Silverlight on a Mac only works within the browser, though he added “I could be wrong”.

In fact, Silverlight out of browser already works on a Mac; the piece that doesn’t work is COM interop, which is not essential to LightSwitch other than for export to Excel. It should not be difficult to run a LightSwitch app out-of-browser on a Mac, just right-click a browser-hosted app and choose Install onto this computer, but Microsoft is marketing it as a tool for Windows desktop apps, or Web apps for any other client where Silverlight runs.

Finally I asked whether the making of LightSwitch had influenced the features of Silverlight or WCF RIA Services themselves. Apparently it did:

There are quite a few aspects of both Silveright 4 and RIA services that are in those products because we were building on them. We uncovered things that we needed to make it easier to build a business application with those technologies. We put quite a few changes into the Silverlight data grid.

said Schmelzer, who also mentioned performance optimizations for WCF RIA Services, especially with larger data sets, some of which will come in a future service pack. I think this is encouraging for those intending to use Silverlight for business applications.

There are many facets to LightSwitch. As a new low-end edition of Visual Studio it is not that interesting. As an effort to establish Silverlight as a business application platform, it may be significant. As an attempt to bring model-driven architecture to the mainstream, it is fascinating.

The caveat (and it is a big one) is that Microsoft’s track-record on modelling in Visual Studio is to embrace in one release and extinguish in the next. The company’s track-record on cross-platform is even worse. On balance it is unlikely that LightSwitch will fulfil its potential; but you never know.

apple, microsoft

Apple iPad replacing PCs as well as paper?

7 Comments

Now here’s an article to strike fear into Microsoft. Stuart Sumner reports on iPad trials at the BBC and in the Army. The BBC’s CIO John Linwood says:

We’re seeding the organisation [with the devices]. We put some iPads into production and some into management and other roles to see if people would be able to give up their desktops.

He goes on to say that the iPad may enable paperless meetings.

What makes an iPad better than a laptop or netbook for a meeting? I find it curious, incidentally, that the report refers to replacing desktops rather than laptops.

Well, one reason I have always liked tablets is that they are more interactive and don’t put a barrier (the screen) between you and others. A stylus is actually nice for meetings – good for quick diagrams as well as handwriting. Apple’s iPad lacks the stylus, but has other advantages over Windows tablets – smaller, lighter, instant-on, long battery life, and so on.

Still, the humble netbook at one third of the price will do the job too, better in some ways. You have Excel, for example. Unfortunately it lacks the elegance, usability and desirability of Apple’s device.

Any excuse to justify handing out cool devices, then? Maybe; but there’s no law that says business equipment has to be dull and unpleasant to use.

amazon, apple, microsoft, mobile, software development

Stats that matter: Android grows in mobile, IE stops declining, eBooks take off

2 Comments

This should be three blog posts; but you’ve read this news elsewhere. Still, I can’t resist a brief comment on three recent trends.

Browsers

The first is that usage of Microsoft’s Internet Explorer has levelled off after a long period of decline. Microsoft says it is increasing but the numbers are too small to say that with confidence. StatCounter global stats for May to July show slight decline for IE (52.83% –> 52.37%) and FireFox (31.54%->30.88%), with Google Chrome the main beneficiary (8.81%->10.32%).

On this blog Chrome has grown from 4.2% to 12.4% in the last year. IE is still declining: 44.9% in July 09, 39.6% in June 10, and 38.2% in July 10.

My guess is that the success of Windows 7 might have brought back a few FireFox users. The interesting story though is where Chrome will be when it stops growing its share. My second guess is that it will be ahead of FireFox, though that is speculative. It is WebKit though, and I think that will be bigger than Mozilla’s Gecko thanks to adoption by Google, Apple, Adobe and others.

Mobile

Next, Google Android. Nielsen reports that it has pulled ahead of Apple iPhone in the US SmartPhone market; both are behind RIM’s Blackberry though that is in steady decline. RIM is announcing Blackberry 9800, the first on OS 6, later today; but I doubt it will disrupt Android’s growth. The developer angle is that Android is now equal to Apple’s iPad/iPhone in strategic importance, which will be a relief to Adobe – Flash runs on Android but not iPhone.

Android owners lack the satisfaction of Apple iPhone owners. 21% of them are eyeing the iPhone for their next upgrade, whereas only 6% of iPhone owners want Android next. Only 42% of Blackberry owners intend to remain loyal. It is all tending to confirm my speculation back in April that Android is the new Windows.

So in two years time, what will be the market share for RIM, Nokia Symbian/MeeGo, Windows Phone, HP Palm WebOS? It will not be easy for any of them.

eBooks

Finally, eBooks. The Kindle vs iPad vs Nook vs Sony is one story; but the bigger one is that the eBook is happening at last. David Carnoy’s recent articles on Amazon give the background. One is an interview with Amazon’s Ian Freed in which the retailer says eBook sales have tripled in the first quarter of 2010 vs that in 2009, and claims 70-80% of the market. Another looks at what Amazon didn’t say. However the market shares work out though, what matters is that screen, battery and wireless technology are now good enough, and publishers and authors willing enough, for eBooks to become mainstream, with huge implications for the media industry.

apple, iphone

Lies, damn lies, and Apple’s antenna-gate

Apple’s iPhone 4 is still relatively new; and I when I pulled it out of my pocket at a social occasion last weekend someone said, “isn’t that the new iPhone?” and another, “isn’t that the one with the aerial fault?”

Another person then showed his iPhone 4, with shattered screen. His had been dropped, an expensive slip of the wrist.

So there we have it, the two worst features of Apple’s new phone – fragility, and a dodgy antenna – exposed to all.

I have first hand-evidence then that the antenna issue is well-known. But how much will it affect sales? I received an email today from Opinium Research. According to their survey of 2000 UK adults, 26% are less likely to get an iPhone 4 because of this widely reported fault.

Pretty bad for Apple then – a quarter of their market gone. Well, no. This is an example of “ask a silly question”. If you ask someone, “does the antenna issue make you more or less likely to buy an iPhone 4,” what do you expect them to say? In fact, 13% of them said it was a non-issue, while 57% said it was irrelevant because they are not in the market for an iPhone 4 anyway.

The right question would be: “Have you changed your mind about getting an iPhone 4 because of the reported fault with the antenna?” I expect many fewer would tick the yes box.

Useless survey then. In my view the phone is fine, the antenna issue is minor, and Apple’s free case offer will sort it for most people.

Going back to my social occasion, by the end of the party Apple had at least one more would-be customer, despite the antenna and despite the fragility; and given that the phone is still out of stock everywhere I don’t think the company need worry too much – though its reaction to this wave of bad publicity has been interesting to watch.

Incidentally, I also had a briefing on Windows Phone 7 today – more on that later.