Tag Archives: iphone

iPhone plus Amazon app = shopping revolution through magic of barcode scanning

Amazon has added barcode scanning to its Apple iPhone shopping app. It is an amazing feature. Here’s why.

Among the questions that shoppers ask themselves, two of the biggest ones are first, is it any good; and second, is it good value? Barcode scanning helps with both of these. The scenario is that you are in the shop looking at a book, CD or DVD – or almost anything really, from kettles to MP3 players – and you wave your iPhone over it. Up comes the entry for that item in Amazon’s store, where you can see the rating, read customer reviews, and check the price both new and used.

OK, there is a little bit more involved than waving the iPhone, but not much. Here is how it works. Tap the Amazon app on the iPhone, then Search.

image 

Tap Scan a barcode and hold the iPhone over the barcode.

image

You adjust the size and position by moving the iPhone until the code is roughly central between the guide lines. At this point, the guide lines turn green.

image

No need to tap; the app will now look up the item and show you the results. Tap the right-pointing arrow for more detail.

image

Confession: I am sufficiently an Amazon addict that I have done this in shops even before the advent of the barcode feature. One reason is price-checking. We all know that you pay a premium for the instant gratification of bricks and mortar shopping; but how bad is it? This will tell you instantly.

That might not help if you need a gift at the last minute, but the reviews might. I use this for video games, or for CDs that I have not heard or DVDs/Blu-rays that I have not seen. It has saved me from some expensive mistakes.

Of course reviews are subjective and some are likely planted by publishers, authors or competitors; but there are usually enough to give you some idea of the range of opinions.

It is also handy for electronic devices. Is that MP3 player any good? How does that iPod dock sound?

When I was at school we learned about the concept of perfect competition. One of the requirements for perfect competition is perfect information – for example, knowing the price charged for an item in every outlet which sells it. We are a long way from that, but thanks to the Amazon marketplace, where third-party sellers compete, we are closer than we were. The barcode feature in the Amazon iPhone app makes it easy to access that information while shopping, which is a big feature.

Apple gives up on Xserve dedicated server hardware – looking towards the cloud?

Apple is scrapping is Xserve products, according to the latest information on its web site:

Xserve will no longer be available after January 31, but we’ll continue to fully support it. To learn more, view the PDF.

If you do indeed view the PDF, it confirms that:

Apple will not be developing a future version of Xserve

However, the Snow Leopard Server, a version of OS X tuned for server use, remains; and Apple suggests that you install it either on a Mac Pro or on a Mac Mini.

image

That’s all very well; but while a Mini might well make sense for a very small business, larger organisations will not be impressed by the lack of features like dual redundant power supplies, lights out management, and rack mounting, which the Xserve provides.

There are a couple of ways to look at this. One is that Apple is giving up on the server market. Largely true, I think; but my guess is that Apple realises that this type of on-premise server is under threat from the cloud. I do not see this as Apple giving up on corporate computing; that would be unexpected considering the gains it is making with Mac, iPhone and iPad. I do see this as a move towards a client and cloud, or device and cloud, strategy. In that context it is not so surprising.

That said, I imagine there are a few businesses out there focused on supplying Xserve-based systems who will be disappointed by the news. I’ve not used one myself; but from what I’ve heard it is rather good.

Windows Phone 7 battles indifference in London

Today is launch day for Windows Phone 7 in the UK – but the hoped-for crowds of people waiting to buy the new phone failed to appear.

They are billed as the handsets that could topple the iPhone. Yet as Microsoft’s Windows 7 phones went on sale this morning there was not a queue in sight.

reported the London Evening Standard.

The device also suffered faint praise from the influential Wall Street Journal reviewer Walt Mossberg. Although he called the user interface “novel and attractive”, he complained about missing features:

Microsoft has inexplicably omitted from Windows Phone 7 key features now common, or becoming so, on competitive phones. These missing features include copy and paste, visual voicemail, multitasking of third-party apps, and the ability to do video calling and to use the phone to connect other devices to the Internet. The Android phones and the iPhone handle all these things today.

adding that

I couldn’t find a killer innovation that would be likely to make iPhone or Android users envious, except possibly for dedicated Xbox users.

Is he right? In some ways it does not matter; perception is reality. That said, none of his missing features strike me as deal-breakers for a majority of users. You can also argue that Microsoft has learnt from Apple not to put every possible feature into the first release, but rather to make the features it does implement work as well as possible and to build on that in the future.

The problem is that there is so much momentum around Google Android and Apple iPhone that the average consumer looking for a smartphone will need a lot of persuading before paying out for Windows Phone 7, or even really noticing it. Microsoft needed rave reviews, not so-so ones. There is a danger that the new phone may suffer the same fate as Palm’s webOS devices, well liked by those who take the trouble to explore them, but absent from the mainstream of consumer consciousness.

I’ve had a device for a few days, and it has been favourably received by people I’ve shown it to. Some of the games look great – The Harvest, for example, a Microsoft exclusive. The Facebook integration is also appealing to fans of that site, and feels deeper than Facebook apps on other devices. Windows Phone 7 does have distinctive features.

I’ll be reviewing the device properly in due course. What is more interesting than my opinions though is how the phone is received in the market. I had expected more interest from the curious on day one of retail release.

Update: Microsoft found a queue or two for its press release today. Big in Australia?

Rethinking Developers Developers Developers

I’m waiting for Microsoft CEO Steve Ballmer to speak at the London School of Economics, which seems a good moment to reflect on his well-known war cry “Developers Developers Developers”.

Behind the phrase is a theory about how to make your platform succeed. The logic is something like this. Successful platforms have lots of applications, and applications are created by developers. If you make your platform appealing to developers, they will build applications which users will want to run, therefore your platform will win in the market.

Today though we have an interesting case study – Apple’s iPhone. The iPhone has lots of apps and is winning in the market, but not because Apple made it appealing to developers. In fact, Apple put down some roadblocks for developers. The official SDK has one programming language, Objective C, which is not particularly easy to use, and unlikely to be known other than by existing Apple platform developers. Apps can only be distributed through Apple’s store, and you have to pay a fee as well as submit to an uncertain approval process to get your apps out there. Some aspects of iPhone (and iPad) development have improved since its first launch. A clause in the developer agreement forbidding use of languages other than Objective C was introduced and then removed, and the criteria for approval have been clearly stated. Nevertheless, the platform was already successful. It is hard to argue that the iPhone has prospered thanks to Apple’s developer-friendly policies.

Rather, the iPhone succeeded because its design made it appealing to users and customers. Developers went there because Apple created a ready market for their applications. If Apple CEO Steve Jobs were prone to shouting words in triplicate, they might be “Design Design Design” or “Usability usability usability”. And as for developers, what they want is “Customers customers customers.”

Well, there are vicious and virtuous circles here. Clearly it pays, in general, to make it easy for developers to target your platform. Equally, it is not enough.

Microsoft’s own behaviour shows a shift in focus towards winning customers through usability, thanks no doubt to Apple’s influence and competition. Windows 7 and Windows Phone 7 demonstrate that. Windows Phone 7 is relatively developer-friendly, particularly for .NET developers, since applications are built on Silverlight, XNA and the .NET Framework. If it succeeds though, it will be more because of its appeal to users than to developers.

What do developers want? Customers customers customers.

RunRev renames product to LiveCode, supports iPad and iPhone but not Windows Phone 7

Runtime Revolution has renamed its software development IDE and runtime to LiveCode, which it says is a “modern descendent of natural-language technologies such as Apple’s HyperCard.” The emphasis is on easy and rapid development using visual development supplemented with script.

It is now a cross-platform development platform that targets Windows, Mac and Linux. Android is promised soon, there is a pre-release for Windows Mobile, and a new pre-release targets Apple’s iOS for iPad and iPhone.

LiveCode primarily creates standalone applications, but there is also a plug-in for hosting applets in the browser, though this option will not be available for iOS.

Now that Apple has lifted its restrictions on cross-platform development for iOS, it is Microsoft’s Windows Phone 7 that looks more of a closed device. The problem here is that Microsoft does not permit native code on Windows Phone 7, a restriction which also prohibits alternative runtimes such as LiveCode. You have to code applications in Silverlight or XNA. However, Adobe is getting a special pass for Flash, though it will not be ready in time for the first release of Windows Phone 7.

If Windows Phone 7 is popular, I imagine other companies will be asking for special passes. The ubiquity of Flash is one factor holding back Silverlight adoption, so in some ways it is surprising that Microsoft gives it favoured treatment, though it makes a nice selling point versus Apple’s iPhone.

Latest job stats on technology adoption – Flash, Silverlight, iPhone, Android, C#, Java

It is all very well expressing opinions on which technologies are hot and which are struggling, but what is happening in the real world? It is hard to get an accurate picture – surveys tend to have sampling biases of one kind or another, and vendors rarely release sales figures. I’ve never been happy with the TIOBE approach, counting mentions on the Internet; it is a measure of what is discussed, not what is used.

Another approach is to look at job vacancies. This is not ideal either; the number of vacancies might not be proportionate to the numbers in work, keyword searches are arbitrary and can include false positives and omit relevant ads that happen not to mention the keywords. Still, it is a real-world metric and worth inspecting along with the others. The following table shows figures as of today at indeed.com (for the US) and itjobswatch (for the UK), both of which make it easy to get stats.

Update – for the UK I’ve added both permanent and contract jobs from itjobswatch. I’ve also added C, C++, Python and F#, (which hardly registers). For C I searched Indeed.com for “C programming”.

  Indeed.com (US) itjobswatch (UK permanent) itjobswatch (UK contract)
Java 97,890 17,844 6,919
Flash 52,616 2,288 723
C++ 48,816 8,440 2470
C# 46,708 18,345 5.674
Visual Basic 35,412 3,332 1,061
C 27,195 7,225 3,137
ASP.NET 25,613 10,353 2,628
Python 17,256 1,970 520
Ruby 9,757 968 157
iPhone 7,067 783 335
Silverlight 5,026 2,162 524
Android 4,755 585 164
WPF 4,441 3,088 857
Adobe Flex 2,920 1,143 579
Azure 892 76 5
F# 36 66 1

A few quick comments. First, don’t take the figures too seriously – it’s a quick snapshot of a couple of job sites and there could be all sorts of reasons why the figures are skewed.

Second, there are some surprising differences between the two sites in some cases, particularly for Flash – this may be because indeed.com covers design jobs but itjobswatch not really. The difference for Ruby surprises me, but it is a common word and may be over-stated at Indeed.com.

Third, I noticed that of 892 Azure jobs at Indeed.com, 442 of the vacancies are in Redmond.

Fourth, I struggled to search for Flex at Indeed.com. A search for Flex on its own pulls in plenty of jobs that have nothing to do with Adobe, while narrowing with a second word understates the figure.

The language stats probably mean more than the technology stats. There are plenty of ads that mention C# but don’t regard it as necessary to state “ASP.NET” or “WPF” – but that C# code must be running somewhere.

Conclusions? Well, Java is not dead. Silverlight is not unseating Flash, though it is on the map. iPhone and Android have come from nowhere to become significant platforms, especially in the USA. Beyond that I’m not sure, though I’ll aim to repeat the exercise in six months and see how it changes.

If you have better stats, let me know or comment below.

Microsoft’s Scott Guthrie: We have 200+ engineers working on Silverlight and WPF

Microsoft is countering rumours that WPF (Windows Presentation Foundation) or Silverlight, a cross-platform browser plug-in based on the same XAML markup language and .NET programming combination as WPF, are under any sort of threat from HTML 5.0.

We have 200+ engineers right now working on upcoming releases of SL and WPF – which is a heck of a lot.

says Corporate VP .NET Developer Platform Scott Guthrie in a Twitter post. Other comments include this one:

We are investing heavily in Silverlight and WPF

and this one:

We just shipped Silverlight for Windows Phone 7 last week, and WPF Ribbon about 30 days ago: http://bit.ly/aB6e6X

In addition, Microsoft has been showing off IIS Media Services 4.0 at the International Broadcasting Conference, which uses Silverlight as the multimedia client:

Key new features include sub-two-second low-latency streaming, transmuxing between H.264 file formats and integrated transcoding through Microsoft Expression Encoder 4. Microsoft will also show technology demonstrations of Silverlight Enhanced Movies, surround sound in Silverlight and live 3-D 1080p Internet broadcasting using IIS Smooth Streaming and Silverlight technologies.

No problem then? Well, Silverlight is great work from Microsoft, powerful, flexible, and surprisingly small and lightweight for what it can do. Combined with ASP.NET or Windows Azure it forms part of an excellent cloud-to-client .NET platform. Rumours of internal wrangling aside, the biggest issue is that Microsoft seems reluctant to grasp its cross-platform potential, leaving it as a Windows and desktop Mac solution just at the time when iPhone, iPad and Android devices are exploding in popularity. 

I will be interested to see if Microsoft announces Silverlight for Android this autumn, and if it does, how long it will take to deliver. The company could also give more visibility to its work on Silverlight for Symbian – maybe this will come more into the spotlight following the appointment of Stephen Elop, formerly of Microsoft, as Nokia CEO.

Apple is another matter. A neat solution I’ve seen proposed a few times is to create a Silverlight-to-JavaScript compiler along the lines of GWT (Google Web Toolkit) which converts Java to JavaScript. Of course it would also need to convert XAML layout to SVG. Incidentally, this could also be an interesting option for Adobe Flash applications.

As for WPF, I would be surprised if Microsoft is giving it anything like the attention being devoted to Silverlight, unless the Windows team has decided to embrace it within the OS itself. That said, WPF is already a mature framework. WPF will not go away, but I can readily believe that its future progress will be slow.

Apple lifts restrictions on app development tools, publishes review guidelines

Apple has lifted its restrictions on the development tools used to create iOS (iPhone and iPad) apps, in a statement published today:

We have listened to our developers and taken much of their feedback to heart. Based on their input, today we are making some important changes to our iOS Developer Program license in sections 3.3.1, 3.3.2 and 3.3.9 to relax some restrictions we put in place earlier this year. In particular, we are relaxing all restrictions on the development tools used to create iOS apps, as long as the resulting apps do not download any code. This should give developers the flexibility they want, while preserving the security we need.

In addition, Apple says it is publishing the App Store Review Guidelines in the hope that this will make the approval process more transparent.

Good news I guess; but why? Maybe in part because the restrictions made little sense and were possibly unenforceable; and in part because Android’s popularity is putting pressure on Apple to be more developer-friendly. In practice, some apps that you would have thought breached the requirements apparently made it through the approval process; and those publishers of cross-platform tools which kept their nerve have their patience rewarded.

But what about Adobe? Apple’s development restrictions seems to trigger a significant change of direction, with work on the Packager for iPhone stopped, Android devices issued to employees, and evangelism for Android in Adobe blogs and tweets.

Since Apple is not changing its mind about runtimes, but only about development tools, this change of mind does not enable Flash on the iPhone; but I guess Adobe could now revive its cross-compilation work. On the other hand, Apple’s pronouncements have caused disruption for Adobe and perhaps served more as a wake-up call: this is a closed platform with one owner and therefore a risky target for investment.

Ten reasons the Apple iPhone 4 beats the Android HTC Desire

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.

Ten ways the Android HTC Desire beats Apple’s iPhone

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.