<![CDATA[Gizmodo: mobile os]]> http://tags.gizmodo.com/assets/base/img/thumbs140x140/gizmodo.com.png <![CDATA[Gizmodo: mobile os]]> http://gizmodo.com/tag/mobileos http://gizmodo.com/tag/mobileos <![CDATA[Microsoft and Palm Treading Water While Other Mobile Platforms Grow]]> It's a great time to be in the smartphone business, unless you're Microsoft or Palm. According to the latest data, they're hardly doing any business at all.

This chart from Fierce Developer shows that while Apple and RIM have been booming, and Symbian and Android have shown decent growth for smaller players, Palm webOS and Windows Mobile have been largely stagnant. Microsoft even managed to lose market share between May and July. At the rate this is going, the two carriers will need some drastic changes to stay in the game. For Palm, the answer could be as simple as an expanded or refreshed product line. For Microsoft, though, it looks like a fix won't be coming any time soon. [Comscore via Fierce Developer via Electronista]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5428233&view=rss&microfeed=true
<![CDATA[“Ballmer says they screwed up with Windows Mobile. Wishes they had already launched WM7."]]> Today at a Venture Capital Summit, Microsoft CEO Steve Ballmer admitted a few things we all already kind of knew: Windows Mobile 7 is late as hell, and needs a lot of work.

Twitter user Beninato quotes Ballmer in saying "This will not happen again" and "We've pumped in some new talent," and Pjozefak gives the blockquote in our headline: Microsoft screwed up with Windows Mobile, and it should have already launched. We've seen a few promising bits previews of Windows Mobile, notably the browser in the Zune HD (it's not perfect, but it bodes well), but Windows Mobile has been a stinker for years now and Microsoft had better bust out the big guns to get it right with WinMo 7. [Twitter and Babbling VC via WMPowerUser via MobileTechWorld via Engadget]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5367358&view=rss&microfeed=true
<![CDATA[Symbian^4 Will Break S60 App Compatibility]]> And this is actually a good thing. Why? Because it means a major Symbian UI redesign is on the way.

TamsS60 spoke with Symbian Foundation rep David Wood, who explained that theyre killing the Avkon UI engine, in favor of Qt, meaning there will be a binary break when it comes to S60 apps. The term "revolutionary" was also thrown around with regard to UI changes. All hope isn't lost yet, Symbian fanboys. Then again, we're probably gonna have to wait another year (at least) for this. [TamsS60 via Engadget Mobile via BGR]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5331111&view=rss&microfeed=true
<![CDATA[AT&T Wants All Its Smartphones Running the Same OS, Eventually]]> AT&T plans to run a single mobile OS on all of its branded smartphones, citing the "support nightmare" of maintaining multiple platforms at once. Curiously, this announcement was made at a Symbian conference. Updated 19:26 EST.

It's not entirely clear what AT&T means by this announcement, but one question was addressed right off the bat: the iPhone, which the company described as "a third-party device" that generally isn't supported or interfered with by the company, is immune. Such a consolidation would push all but one of Microsoft, RIM, Nokia or even Google out of AT&T's stable, which might be construed as brash.

Even more bizarre are the implicit expectations for phone manufacturers. Would RIM, assuming their phones aren't deemed "third party products", be expected to adopt a new OS? Will Nokia phones be excluded from AT&T's lineup unless they run Windows Mobile? Simultaneously stating that the plan would only include AT&T branded smartphones (of which there are few) and that it would be a "dramatic restructuring", the company has left the scope of this initiative a mystery.

As for which OS would be chosen, the location of the announcement and mentions of a preference for an "open" platform are all we have to go on. I could imagine these statements raising a few eyebrows around the industry, so don't be surprised to see some kind of clarification issued in the next few days. [Yahoo]

UPDATE: Although it is possible some quotes in the original story came from a post-speech interview with AT&T's Roger Smith, commenter Sinecure saw the presentation and took awy a completely different message:
I sat through the entirety of Roger Smith's presentation at the Symbian show yesterday and I did NOT come away with that impression one single bit. Methinks some Yahoo reporter just got a little over-excited for an interesting headline. I'm calling major BS and misinterpretation on this one.

Frankly it makes me even more suspect of some of the reporting on technical subjects out there.

Bottom line: I heard this supposed "announcement" first hand and I did not hear him say anything approaching what the reporter is saying.

UPDATE II: And now for that clarification I was talking about. AT&T's statement on the matter:
We have no plans to standardize on one platform for our smart devices.

We want to give our wireless customers maximum choice – in innovative devices, applications, operating systems, and more. One way to maximize customer choice is to begin to reduce fragmentation in the wireless OS environment. That is why we are a member of the Symbian Foundation.

That fragmentation puts a heavy burden on wireless carriers, handset makers, and especially apps developers, who have to create for multiple operating systems and sometimes for multiple versions of the same operating system.
]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5102331&view=rss&microfeed=true
<![CDATA[An In-Depth Video Tour of Android 0.9, an (Almost) Great (Almost) OS]]> Earlier today Google released the Android 0.9 SDK r1 Beta, boasting of a pile of API updates and a visual refresh that moves it one solid step closer to actually, you know, showing up on a phone. A long changelog and a few screenshots are great, but we've fired up the SDK's emulator for a guided tour of Android's salient features.

0:02: Main menu is contained in a drawer that slides from the bottom of the screen
0:08: Multiple home screens can be flipped with touch gestures, a la the iPhone
0:20: Icons can be dragged from the main menu to build customized home screens. Dragging to the menu drawer trashes the home screen shortcut
0:38: Dialer screen, followed by the call behavior. Calls can continue in the background, and all functions that don't require data transfer can work concurrently (This is currently a software regulation, as 3g networks should theoretically allow for simultaneous voice and data usage).
0:53: Ongoing calls and other notifications can be accessed by dragging the taskbar down.
1:20: Browser displays Gizmodo. Rendering is quite good, page navigation is a fairly intuitive rehash of current touch-control schemes. It's not terrible good at guessing column widths during double-tap zooming, but seems very usable. Preview magnification feature is useful for smaller screens or text-heavy pages.
2:22: "Tabbed" browsing feature lays out a grid of pages, with previews
2:45: Google Maps app. As you can see, this is among the more polished apps, and will feel familiar to anyone who has used Google Maps on the desktop or mobile devices.
3:30: Google Maps Street View.
4:00: Home screen include widgets (Google Search, a clock and a picture frame are the only ones for now) that can be dragged around the home screen(s).
4:23: The music apps relies on a panel of icons (a recurring theme in Android)
4:30: Message composition is unremarkable, but there is no sign of an on-screen keyboard at the moment. This could be a customization catered the the first round of Android phones, at least one of which will have a slide-out keyboard.
5:12: The camera naturally doesn't work in the emulator, but there are currently very few options in its menus.
5:50: Wallpaper switching. This is one of the few areas where Android excels aesthetically. Wallpaper scrolls as home screens are switched, but at a slower rate that the icons. This creates a convincing illusion of depth.
6:11: The home screen can also be modified via the system menu, where you can choose to add applications, widgets and shortcuts, as well as change the wallpaper.

It's hard to pass judgment on Android in the condition it's in. What's there is impressive, but there are so many glaring omissions, at least from a consumer standpoint. There is a fantastic system for managing ongoing calls and system messages (via the pull-down taskbar) but no apps to take advantage of it. Email and IM would suit such a configuration beautifully, but neither is included in this release. And seriously, where is the calendar? The organizer? A video app? Youtube support?

Sure, these things could be left to the developer community, but Google already has messaging, email, video and calendar services, so it's reasonable to expect that they be included by default in Android. Before a public release, Android should at least possess a feature set comparable to your average candy bar phone, courtesy of Google, so that the eager open-source development community can devote their effort to creating new, innovative apps and modifications for the OS.

Objections aside, the progress is promising. In terms of usability, Android is much easier to navigate and customize than virtually all other mobile solutions. With a few more apps, Android will be a clear choice over Windows Mobile, skinned or not. You can download the SDK and play with the emulator yourself, if you want. Just a word of warning, though — explaining to your family or significant other that you're testing an emulated prerelease of an upcoming mobile OS is about as hard as it sounds. [Google Android, Android on Giz]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5038586&view=rss&microfeed=true