Tag Archives: mobile

15 minutes with the Nintendo 3DS

Today I got to try a Nintendo 3DS for the first time. A few first impressions.

It is a neat unit though it feels a little flimsy compared to the original DS or the DS Lite. I like the charging dock that comes in the box. Here it is, complete with genuine user fingerprints. The joystick (or circle pad) on the left is beautifully responsive.

image

My first question was: what is the 3D like? The answer is that it really works.

I spent some time playing with the Augmented Reality game, where you lay cards on a table, point the 3DS rear cameras at them, and see magic happen as three dimensional creatures emerge, intermingled with the real world around them.

Photographing this takes more skill than I possess, but to give you the idea, here are four Augmented Reality cards (all in the box as standard) that I have laid on the desk:

image

and here is a snap of the 3DS top screen viewing those cards in the AR game:

image

You cannot see it from this image, but the 3D effect is vivid, and the background is the desk on which the cards are placed. A gimmick, but an engaging one.

The built-in AR game is a lot of fun and makes use of the AR background in that you have to pan the camera around the targets to shoot successfully, something which cannot be reproduced in a purely screen-based game.

What about eye strain? I am not sure; but the 3D screen did seem to strain my eyes slightly. There is a slider which lets you reduce or disable the 3D effect easily, so the eye strain possibility should not deter you, except that since you are paying for a 3D device it is a shame not to use it.

There is a lot more packed into the 3Ds though. It has an accelerometer and gyroscope, one front and two rear (for 3D) cameras, and wireless LAN that supports WPA/WPA2 at last – this was an annoyance with the older WEP-only models.

The software has the usual Nintendo quality, complete with the ability to create Mii avatars similar to those on the Wii, but this time they can be based on a snapshot of someone’s face taken with the built-in camera.

The downside versus the original DS is the battery life – just 3-5 hours.

Still, DS fans will love the 3DS. But will it grow its market? I’m doubtful. A lot of the market for casual gaming has passed to smartphones now; and for someone with a modern smartphone, the 3DS duplicates a lot of functionality. Few smartphones have 3D of course, though I did see the LG Optimus 3D at Mobile World Congress last month.

But how important a feature is 3D? That is an open question, and I guess depends on how much difference it makes to gameplay. My quick impression is that while it is truly impressive when first encountered, it is something you soon feel you could manage without – but that is only a quick impression and I could be proved wrong.

Adobe AIR 2.6, MonoMac 1.0, cross-platform is not dead yet

It is a busy time for cross-platform toolkits. Adobe has released AIR 2.6, and reading the list of what’s new you would think it was mainly for mobile, since the notes focus on new features for Apple iOS, though AIR is also a runtime for Windows, Linux and desktop Mac. New features for iOS include GPU rendering – a form of hardware accelerated graphics – access to the camera, microphone, and camera roll, and embedded Webkit for apps that use web content. On Google Android, you can now debug on devices connected via USB.

There is also a new feature called “owned native windows” which lets you have a group of windows that remain together in the Z order – this lets you have things like floating toolbars without odd results where toolbars get hidden underneath other applications.

Asynchronous decoding of bitmaps is another new feature, allowing images to be processed in the background. This seems like a stopgap solution to overcome the lack of mullti-threading in AIR, but useful nonetheless.

Since the Flash runtime does not run on iOS, Adobe has a packager that compiles an AIR application into a native app. This is now called the AIR Developer Tool or ADT. You can use the ADT to target Windows, Linux or Android as well; however platforms other than iOS still need the AIR runtime installed.

Adobe is dropping support for the original iPhone and the iPhone 3G. iPhone 3GS or higher is needed.

If you want to build a cross-platform app but prefer .NET to Adobe’s Flash and ActionScript, the Mono folk have what you need. I’d guess that the Mono team has a small fraction of the resources of Adobe; but nevertheless it has delivered MonoTouch for iOS and is working on MonoDroid for Android. Just completed in its 1.0 version is MonoMac, for building Cocoa applications on Apple OSX. Mono is not fully cross-platform, since the GUI framework is different on the various platforms, but you do get to use C# throughout.

I am happy to agree that true native code is usually a better solution for any one platform; but at a time when the number of viable platforms is increasing the attraction of cross-platform has never been greater.

The future of Google Apps: social features, high performance spreadsheets, working offline

Yesterday I spoke to Google’s Global Product Management Director for Google Enterprise (whew!) Matthew Glotzbach, at a press briefing for Google Apps which included the announcement of Google Docs Discussions, as covered here.

image_thumb

One of the issues discussed in the briefing was Cloud Connect, which I reported on here. Cloud Connect automatically copies and synchronises Microsoft Office documents with Google’s cloud storage. There are some performance and usability issues, but the biggest problem is that you cannot edit the documents in the browser; or rather, if you do, Google makes a second copy leading to versioning issues.

Google says this is a file format issue. The online Google Docs applications cannot edit documents in Microsoft Office formats – “the document models are completely different” says Glotzbach – though it can import and export those formats. Could Google develop the ability to edit Office documents online? “It is a technical challenge, something we haven’t built yet,” he added.

It is an interesting point. Microsoft’s Office Web Apps have flaws, but they do let you maintain the same document whether edited in the browser or in the Office desktop applications. It is an example of friction if you try to live partly in Microsoft Office, and partly in Google’s cloud. It may be better to stick with one or the other.

What about offline capability, something I hear a lot as counting against Google Docs. Google had a solution for this based on its Gears add-on, but then withdrew it.

We are actively working on offline. It is extremely important. Gears was a precursor. A lot of the ideas embedded in Gears have become part of HTML5.

says Glotzbach. I asked whether this will extend to the Chrome OS netbook operating system, and he said that it will:

Chrome, as the most modern browser based on HTML 5, has the capabilities built into its core. Chrome OS as a derivative of that has those offline capabilities baked into it, so it is a matter of having applications take advantage of that.

We also talked about the new discussions feature. I observed that it seems to be just one part of a bigger story. What about discussions spanning multiple documents? What about discussions without documents? Is there any way of doing that?

“Yes, email,” he said, chuckling. Clearly Google has taken to heart that email remains the de facto mechanism for most corporate collaboration. “We’ve also got Google groups. Obviously the manifestation of a group for many users is email, that’s how they interact with it, but there is also a destination site or page for that group.”

Might Google develop its own equivalent to Salesforce.com Chatter, for Twitter-like enterprise messaging?

The idea of eventually being able to pull in other streams, the idea of social media inside the enterprise Is a powerful idea. I think Chatter is a good example of that, and others such as Yammer. I think those ideas will likely find their way into businesses. It is not clear to me that social will be a destination within an Enterprise. Rather I see it as, features will emerge in various products that leverage those social capabilities. Discussions is influenced heavily by a lot of those social media ideas, and so you can see that evolving into more integrated social capabilities across the app suite.

What about Google spreadsheets, which seem great for simple tasks and collaboration, but suffer performance and scalability issues when used with large data collections that work fine in Excel?

There’s always work to do. We have today some limitations in terms of spreadsheet size. Those are things we are actively working on. With browser technologies I actually think we have an advantage over desktop applications. If I told you I had a spreadsheet that had 5 million columns and a billion rows, there’s no desktop spreadsheet in the world that can handle that kind of volume, but because we have in essence supercomputers on the back end processing that, what you display is just a window of that large data. So we’re using clever technologies like pre-fetching the rows and columns that are just off the edge of the page, similar to some of the technologies we use with Google Maps.

But it’s an example where we have some artificial limitations that we are working to remove. Imagine doing really sophisticated non-linear calculations in a spreadsheet. We’ve got a supercomputer on the back end that can do that for you in seconds.

Microsoft’s stumbling Windows Phone 7 launch – from a fan

Danny Tuppeny’s post on Why I’m Close to Giving Up on Windows Phone 7, as a User and a Developer is worth a read. He describes his experience as a Microsoft-platform developer who is a natural enthusiast for Windows Phone, except that he has been unimpressed with how its launch has been handled.

The first thing he noticed was its lack of visibility on the high street – something I have also observed:

I popped into a Carphone Warehouse over the road from the office where I work on launch day. The staff knew nothing about WP7. I called all the local Orange stores, hoping for a HTC Mozart. Nobody knew when, or if, they would be getting any Windows Phone 7 devices. Wow.

That was not necessarily Microsoft’s fault. It had to convince its operator partners to promote the phone, and they had to convince retailers. All difficult with a launch device, in a market all-but sewn up by Apple and Android between them.

Over to Microsoft then, to convince the world of the value of its device. What would it take? Microsoft needed a start-up mentality. Total commitment to its mobile platform. Regular updates and bug-fixes. Responsive support.

As time went on, cracks started to show. There were bugs. Many bugs. At one point, the SMS message store for my wife got corrupt, which meant I couldn’t send, or read, text messages to/from her. I got in touch with the UK WP7 developer advocate that had sorted out the developer phone for my company, and explained the issue. After many emails going back and forth I was told that there may be logs on my phone that would help Microsoft track down this issue but security procedures do not allow them to share a tool to get the logs off my device. I was instead, told to try a factory reset. This fixed the issue, but Microsoft were no closer to finding/fixing the bug.

So what Tuppeny experienced was the opposite of start-up mentality; rather, the frustration of dealing with a huge corporation.

Next, he was disappointed by delays to the Windows Phone 7 update, promised at launch, that would add copy and paste to the operating system:

The update was delayed. And delayed. There was zero transparency from Microsoft. Despite the rest of the company making huge strides in this area over the previous few years, Windows Phone 7 is a quiet, closed box. Nobody knew what was happening with the update, and more importantly, the bug fixes.

He is not giving up:

I’m not giving up, just yet. I truly believe Windows Phone 7 can be something brilliant, but there are definitely issues that need addressing. To show how seriously I believe Microsoft could make this work, I’ve applied to go and work for the Windows Phone team.

My own perspective on this is that Microsoft as a whole does not convey commitment to its mobile platform. How can this be, when CEO Steve Ballmer makes a point of hyping the phone at events like CES and Mobile World Congress? Well, I ask myself why Microsoft has refused to use the Windows Phone 7 OS in a tablet form factor, for which it seems well suited; and I ask myself how the phone OS can survive if Windows 8 is launched on a multitude of different form factors and device types. Paul Thurrott says it:

I can and have speculated that Sinofsky, as the dominant sub-CEO executive at Microsoft now, will simply swoop in and dismantle WP when Windows 8 is ready, but that is just an uneducated outside opinion, nothing more.

That may well not be the case; but the mere fact that some signs point towards it undermines the platform.

If I were Nokia this would worry me; except that Nokia may also in fact plan to embrace some new Windows 8 thing when the time comes, and one presumes that Microsoft has shared more of its future plans with Nokia’s executives than it has with the rest of us.

The Apple iPad post-PC era in education

I am at the QCon conference in London where I attended a session by Fraser Spiers mysteriously titled The Invisible Computer Lab.

Spiers is the guy who won a certain amount of fame or notoriety by issuing all staff and pupils with Apple iPad devices at the Scottish private school where he teaches computing.

image

The session blurb did not mention the iPad but said, “this talk will argue for a new direction in school ICT.” I went along because I am conscious that the way computing is taught in UK schools is often ineffective. Problems include kids knowing more than teachers; out of date hardware; too much Microsoft Office; and often an exclusive focus on general purpose applications rather forming any understanding of what computers are and how they work.

There is probably a connection between this and the low interest in computer science in higher level education.

Spiers did mention this; but most of the talk was an iPad love-in. He is an Apple fan and showed us pictures of the original iMac and various Mac notebooks which preceded the arrival of the iPad at his school.

Nevertheless, he made a persuasive case for how the iPad had transformed teaching (not only computing) at the school. According to Spiers, the children write longer essays because they have discovered word processing for the first time; they have new artistic creativity; they use the web far more and the school had to upgrade its internet connectivity; they are escaping from a word-based approach to learning and presenting their work to one which makes use of multiple media types.

He added that some of the expected snags did not materialise. They were concerned about the virtual touch keyboard on the iPad and offered keyboard accessories to everyone; but in practice few wanted it. The kids, he said, now dislike plastic keyboards with their tiresome buttons.

It is not a new model of computing, it is a new model of education. Handwriting may longer be an important skill, said Spiers.

Now, I do make due allowance for the over-exuberance of an Apple evangelist; and that the reality may not be as rose-tinted as he describes it.

At the same time, you can see how well Apple’s controlled computing environment works in a school environment, where kids may try to break computers or do bad things with them, as well as how the design and usability revolution plays out in a school environment.

Note, however, that Apple is not yet really geared up for iPad in education and Spiers encountered silly issues like the inability to buy site licences for apps delivered over iTunes; each one has to be purchased individually, and they have to fudge the accounts since nobody under 13 can use the app store. I am sure issues like this will be fixed soon.

Objections? Well, there is the cost of Apple’s premium hardware and its tax on the software. There is the ethics of using Apple at all – today, as it happens, there are posts by Bill Thompson and by Tom Arah which do a good job of spelling out concerns about Apple’s authoritarian and increasingly greedy business practices, especially with iOS and the App Store. I would rather be writing up the impact of Linux or Android or open source in education.

However, I will close with my question to Spiers and his answer. What will happen, I asked, when these kids with their experience of iPad computing get jobs and are confronted by offices full of PCs?

“A child that starts this year is going to graduate in 2024,” he replied. “I don’t know what the business environment is going to be like in 2024. I think there will be convergence between iOS and the Mac. I think businesses that stick with the PC infrastructure will not be around in 2024.”

Mono project: no plans for cross-platform WPF

Miguel de Icaza’s report from the Game Developer Conference is upbeat, rightly so in my view as usage of Mono is continuing to build, not only in game development with Unity, a development tool that uses Mono as its scripting engine, but also for mobile development for Apple’s iOS with Monotouch and for Android with Monodroid. These mobile toolkits also give Mono a stronger business model; many sites use Mono for serving ASP.NET applications on Linux, but without paying or contributing back to the project.

Mono is an open source implementation of C# and Microsoft’s .NET Framework.

That said, it is interesting that Mono is still struggling with an issue that has been a problem since its first days: how to implement Microsoft’s GUI (Graphical User Interface) framework on other platforms. Mono does have Gtk# for Windows, Mac and Linux, but this does not meet the goal of letting developers easily port their Visual Studio client projects to Mono. There is also an implementation of Windows.Forms, but de Icaza mentions that “our Windows.Forms is not actively developed.”

Apparently many tools vendors asked the Mono team at GDC when Windows Presentation Foundation (WPF) would be implemented for Mono. WPF is the current presentation framework for Microsoft.NET, though there is some uncertainty about where Microsoft intends to take it. I remember asking de Icaza about this back in 2003, when the WPF framework was first announced (then called Avalon); he said it was too complex and that he did not plan to implement it.

This is still the case:

We have no plans on building WPF. We just do not have the man power to build an implementation in any reasonable time-frame.

That said, Mono has implemented Silverlight, which is based on WPF, and there are some signs that Microsoft might merge WPF and Silverlight. What would the Mono team do then?

Miguel de Icaza says:

Silverlight runs on a sandbox, so you can not really P/Invoke into native libraries, or host DirectX/Win32 content inside of it.
There are other things missing, like menubar integration and things like that.

Of course, this is no longer true on Windows: Platform Invoke is coming in Silverlight 5.

Perhaps the Mono team will knuckle down and implement Silverlight with desktop integration, which would be good for cross-platform Silverlight and compatibility with Microsoft .NET.

Then again, it seems to me that Mono is increasingly divergent from Microsoft .NET, focusing on implementing C# in places that Microsoft does not touch, such as the mobile platforms from Apple and Google.

That is actually a sign of health; and you can understand why the Mono team may be reluctant to shadow Microsoft’s every move with Silverlight and WPF.

Google fails to protect its mobile platform

The discovery of viruses in apps on Google’s Android Market is troubling. I like the fact that Android is open, and that you can easily install an APK (Android Package) from any source onto your device if you want to. That said, it is reasonable to expect that apps downloaded from the official Android Market will be virus-free, or at least that some attempt has been made to check them for malware.

Another problem which is apparently rampant in the Android market – and also to some extent in Apple’s app store – is app stealing, where someone takes an existing app, copies and re-uploads on their own account. In most cases it seems that the malware was on apps pirated in this manner.

Note that while it took Google less than five minutes to pull the malicious apps from the store, the original developer had apparently been trying for more than a week to get them pulled on copyright violation grounds.

Google takes 30% transaction fee for apps sold in the market. Enough, you would think, to check for malware.

Most seriously for the Android market, the situation for users is that apps on Android Market might be malware, whereas apps on Apple’s App Store are not. That is a big advantage for Apple, and one that you would have thought Google would want to counter.

The only winners here are the anti-virus companies, who will be delighted to inflict their subscriptions on mobile users just as they have on Windows desktops.

Appcelerator releases Titanium Mobile 1.6

Appcelerator has released Titanium Mobile 1.6, an update to its cross-platform app framework for Apple iOS and Google Android.

The update adds 26 features for Android and 9 features for iOS. The Facebook API has been completely redone, keeping up-to-date with the latest Facebook API. There is beta support for the Android NDK – native code development.

Android 1.6 is now deprecated and will not be supported in future releases.

While not a big release in itself, Titanium Mobile 1.6 is require for using forthcoming Titanium+Plus modules, libraries which add support for features such as barcode reading and PayPal payments.

There is no sign yet of Aptana integration, following the acquisition of this JavaScript IDE in January.

Updating to the 1.6 SDK was delightfully easy on Windows. Just open Titanium Developer and click the prompt.

image

First look at HP’s TouchPad WebOS tablet

I took a close look at HP’s WebOS TouchPad tablet during Mobile World Congress in Barcelona.

This 9.7” machine looks delightful. One of its features is wireless charging using the optional Touchstone accessory. The same technology can also transmit data, as mentioned in this post on wireless charging, and the TouchPad makes use of this in conjunction with new WebOS smartphones such as the Pre3 and the Veer. Put one of these devices next to a TouchPad and the smartphone automatically navigates to the same URL that is displayed on the TouchPad. A gimmick, but a clever one.

image

From what I saw though, these WebOS devices are fast and smooth, with strong multitasking and a pleasant user interface. Wireless charging is excellent, and a feature you would expect Apple to adopt before long since it reduces clutter.

I still would not bet on HP winning big market share with WebOS. The original Palm Pre was released to rave reviews but disappointing sales, and HP will have to work a miracle to avoid the same fate.

Motorola Atrix – the future of the laptop?

I took a closer look at the Motorola Atrix on display here at Mobile World Congress. This is a smartphone built on NVidia’s Tegra 2 dual-core chipset. I’m interested in the concept as much as the device. Instead of carrying a laptop and a smartphone, you use the smartphone alone when out and about, or dock to a laptop-like screen and keyboard when at a desk. The dock has its own 36Wh battery so you are not tied to mains power.

image

image

image

The Atrix has a few extra tricks as well. HDMI out enables HD video. An audio dock converts it to a decent portable music player.

image

The smartphone also morphs into a controller if you use Motorola’s alternative dock, designed for fully external keyboard and screen.

image

It is a compelling concept, though there is a little awkwardness in the way Motorola has implemented it. The Atrix has two graphical shells installed. One is Android. The other is a an alternative Linux shell which Motorola calls Webtop. While you can freely download apps to Android, the Webtop has just a few applications pre-installed by Motorola, and with no official way to add further applications. One of them is Firefox, so you can browse the web using a full-size browser.

The disconnect between Android and Webtop is mitigated by the ability to run Android within Webtop, either in its own smartphone-sized window, or full screen.

Personally I prefer the idea of running Android full screen, even though it is not designed for a laptop-sized screen, as I do not like the idea of having two separate sets of apps. That seems to miss the point of having a single device. On the other hand, Webtop does enable non-Android apps to run on Atrix, so I can see the value it adds.

Leaving that aside, I do think this is a great idea and one that I expect to become important. After all, if you do not think  Tegra 2 is quite powerful enough, you could wait for some future version built on the quad-core Tegra 3 (name not yet confirmed), which NVidia says is five times faster, and which may turn up in Smartphones late in 2011.