≈ Relations

As (nearly) anybody else working in media i  am discussing its implications nearly every day at work. Here’s the management summary of  my current state of mind:

• Tablets will be gamechangers  both for personal media consumption and personal computing (if executed right)
• Neither re-enacting /emulating existing media (especially in the newspaper and magazin space) nor re-enacting existing personal computing user experiences will do the trick. “Enhanced editions” of all kinds where one of the most talked about topics at O’Reilly’s Tools of Change for Publishing conference in late February.
• Most media companies have a long way to go until they are tablet-ready. And that means wrt. enabling their existing processes and content, not wrt. building exciting apps. The prior are a necessary precondition for the latter.
• It is nearly impossible to do development for tablets without a physical device. Because good applications wil be based on making the experience as physical  as possible. And that means integrating sensors of all kind as well as direct manapulation interfaces

Apples Human Interface Guidelines

Carefully reading  the iPad Human Interface Guidelines  is presumably the best thing you can do in order prepare for developing iPad applications. Thankfully uxmag published the overview  of these guidelines first. Hence i’m feeling quite confident that i might publish them over here without getting litigated from Apple (technically even these guidelines  are under NDA and only available to members of the iPhone / iPad developer program):

Support All Orientations

Your application should encourage people to interact with iPad from any side by providing a great experience in all orientations. The reason is that people don’t view the device as having a default orientation, because they don’t pay much attention to the minimal device frame and they’re unconcerned with the location of the Home button.

Enhance Interactivity (Don’t Just Add Features)

The best iPad applications give people innovative ways to interact with content while they perform a clearly defined, finite task. Resist the temptation to fill the large screen with features that are not directly related to the main task. In particular, you should not view the large iPad screen as an invitation to bring back all the functionality you pruned from your iPhone application.

Flatten Your Information Hierarchy

Although you don’t want to pack too much information into one screen, you also want to prevent people from feeling that they must visit many different screens to find what they want. In general, focus the main screen on the primary content and provide additional information or tools in an auxiliary view, such as a popover.

Reduce Full-Screen Transitions

Instead of swapping in a whole new screen when some embedded information changes, update only the areas of the user interface that need it. When you perform fewer full-screen transitions, your application has greater visual stability, which helps people keep track of where they are in their task.

Enable Collaboration and Connectedness

Think of ways people might want to use your application with others. Expand your thinking to include both the physical sharing of a single device and the virtual sharing of data.

Add Physicality and Heightened Realism

Whenever possible, add a realistic, physical dimension to your application. The more true to life your application looks and behaves, the easier it is for people to understand how it works and the more they enjoy using it.

Delight People with Stunning Graphics

The high-resolution iPad screen supports rich, beautiful, engaging graphics that draw people into an application and make the simplest task rewarding.

De-emphasize User Interface Controls

Help people focus on the content by designing your application UI as a subtle frame for the information they’re interested in. Downplay application controls by minimizing their number and prominence. Consider creating custom controls that subtly integrate with your application’s graphical style. In this way, controls are discoverable, but not too conspicuous.

Minimize Modality

iPad applications should allow people to interact with them in nonlinear ways. Modality prevents this freedom by interrupting people’s workflow and forcing them to choose a particular path.

Rethink Your Lists

Consider a more real-world vision of your application. For example, on iPhone, Contacts is a streamlined list, but on iPad, Contacts is an address book with a beautifully tangible look and feel.

Consider Multifinger Gestures

The large iPad screen provides great scope for multifinger gestures, including gestures made by more than one person.

Consider Popovers for Some Modal Tasks

If you use modal views to enable self-contained tasks in your iPhone application, you might be able to use popovers instead.

Restrict Complexity in Modal Tasks

People appreciate being able to accomplish a self-contained subtask in a modal view, because the context shift is clear and temporary. But if the subtask is too complex, people can lose sight of the main task they suspended when they entered the modal view.

Downplay File-Handling Operations

Although iPad applications can allow people to create and manipulate files and share them with a computer (when the device is docked), this does not mean that people should have a sense of the file system on iPad.

Ask People to Save Only When Necessary

People should have confidence that their work is always preserved unless they explicitly cancel or delete it. If your application helps people create and edit documents, make sure they do not have to take an explicit save action.

Start Instantly

iPad applications should start as quickly as possible so that people can begin using them without delay.

Always Be Prepared to Stop

Like iPhone applications, iPad applications stop when people press the Home button to open another application.

Adobe and HPs (lack of) vision

Meanwhile Adobe and HP join forces and publish a video previewing Adobe running on a HP Slate. Not surprisingly they are focusing on the “full web” experience that is enabled by runing a “real” operating system running “real” web sites and “real” applications (based on Adobe AIR).

Meaning: Cluttered OS build for a different kind of system (PC/Laptop) using a different user interface metaphor (Desktop/Mouse) showing websites optimized for both.

IMHO especially the photoshop.com demo in the video below clearly shows the lack of vision and violation of the “De-emphasize User Interface Controls” Guideline from above.

PS.: More dissemination of the video (as well as an alternative takeon it) can be found at crunchgear

My $0.02 (first edition)

The perfect device for baby boomers and pensioneers

As i already twittered : It looks like the perfect device for my mother (just turned 80).I always did not set-up a computer for her (although i’m storing a couple of my old ones at her home). It would just have been too complicated for her. Still she is very interested to learn about that internet thing. And as her eyes got worse she is not able to easily read the newspaper or regular size books.

Others agree:

• A colleague walked into the office yesterday morning, saying: “Now we know what to buy for our parents.”
• More on this for example on jageree.com and Ultimi Barbarorum

A future version will probably add a camera (jointly with a camera for the iTouch) and grandma’s are able to have iChats with their siblings and friends.

A home and an away version

I’m happy to see  a  WiFi only version of the iPad as well as a full mobile version. i already have an iPod Touch and an iPhone and have complementary uses for them at home and away.

I’m not too happy to have no GPS in the WiFi device because with offloaded Maps i would love to use it also in the car or on holiday etc (Romaing charges are just ridiculous high in europe, so i typically offload maps of the region before going on holiday)

A lost opportunity

A lot of people are complaing about missing features. I typically don’t because i firmly believe in simplicity. There are exceptions (see e.g. above).

But right now i think Apple lost an opportunity to not add a MiniDisplay Port and or micro USB port as video and serial connector. May be even add  a third  proprietary connector if neede.

Placed them side by side and  they would not need more  room on the device than the 30-pin connector.   You  could even build an  dongle to convert the threesome to a 30-pin connector in order to  be able to  the existing iPod accessories.

I know it would potentially cannibalize the existing iPod  3rd Party ecosystem (you wouldn’t if you build / sold the above dongle.

But having separat small standard ports would:

• make the connector cables much more elegant (no bulky dongles)
• beam the  port capabilities into the current time
• especially would enable digital video out. I suspect that the A4 SoC is perfectly able to do digital video, but  having only analog video out has mainly to do with the aging 30-port connector. It may also have to do with making content providers happy)

Open Questions

These have mostly to do  with my professional view on the iPad (as the head of the R & D lab of one of the worlds largest newsagencies currently looking very hard at ereading:

• When will iBooks be available outside the USA?
• Will it offer subscription based pricing models that magazines and newspapers can use (although the app is called iBooks? But we also got used to buy videos etc. in an app called iTunes :-)
• Will the SDK contain classes for rendering ePubs or will tht be private to iBooks?
• Will ePubs automatically opened with iBooks?
• …

Misc

iBooks looks an awful lot like Delicious Library (as others have olso noted). Could swear that Mike Matas (the original designer of Delicious Library that joined Apple in 2005) had a hand on it. But then learned that Matas left Apple  in July 2009.

On Monday Apple finally sent out the invites  to their January 27th event – widely presumed to be about the RAT  (Rumored Apple Tablet). Because everyone and their dog is speculating about what the RAT  would or not would be i just like to point you to the summaries that I think most likely  are to be correct for most of their parts: Andy Ihnatko (from which i shamelessly stole the RAT acronym above) and John Gruber (Part I and Part II).

Whatever exactly will be announced by Apple (and even if they wouldn’t announce a tablet at all) i’m sure that 2010 will be the year of the tablet, as much as 2008 was the year of the netbook. Because 2010 is (finally) the year of the confluence of all the necessary technologies.

Let’s have a look:

Processors

RightNow there is a multitude of powerful (mostly multicore) processor platforms out there that consume very little power and are still able to en/decode HD video, driver large displays and do 3D-rendering and integrate WiFi / GSM. Most notable the Nvidia Tegra 2, Marvells Armada 510/610, Qualcomms Snapdragon,  TI’s OMAP and Freescales i.MX. Important: Practically all of them are ARM-based.

Displays

Touch-enabled displays are now available in all sizes ranges that are of interest for tablets: 5”, 7” and 10”.  There are two power-saving display technologies that are production ready in 2010: AMOLED (Active Matrix Organic Light Emitting Diode) and PixelQis transflective displays. They are somewhat complementary. While AMOLEds excel at displaying bright  images /video and are available at a reasonable price for 5” (and to some extent at 7” display sizes but practically out of scope for 10” displays, PixelQi’s transflective displays in their reflective mode are practically equal to e-ink displays wrt. display crispness and readability in sunlight (while still able to display video), and equal to normal LCD displays  in transmissive mode. They are right now manufactured in 10”.

OS

Open Source, Linux based, fast booting OS have also evolved to a quality  where they are mass compatible. Most notable Android (a Linux / Java Based OS) has been picked up by most mobile phone manufacturers and also gets traction in into mobile internet devices / tablets (see below). Other contenders are Google Chrome OS /Chromium, Moblin / Ubuntu Moblin Remix and  Maemo.

CES 2010

I ended my July 2008 blog post  titled  “Will Apple finally my dream e-reading /netbook device” with:

We’ll see. If not (Ed. Apple is building a tablet), hopefully somebody uses Google’s android to build such a device.

Fortunately, this is exactly what is happening and could be seen at CES2010. Partly by replacing Androind with another of  the OS alternatives  mentioned above. Forget the lame MS/HP presentation, the real action could be seen elsewhere and nearly everywhere (because of the confluence of the technologies i mentioned above).

So without further ado some pointers to my favorite exhibits at CES2010 (sometimes also other events)

10” devices

My personal highlight of CES2010 was NotionInk ADAM, a 10” tablet based on NVidia Tegra 2, PixelQi Display and Android

Notion ink ADAM

More about the device can for example be found here.

The PixelQi Display has also been shown integrated into a Lenov Idea Pad. The video below is especially interesting because it shows the two different display modes using the NYT Reader 2.0 app.

7” devices

MSI Wind has show prototypes of both 10” and 7” dualscreen devices. The video below shows the 10” version as the 7” version was seemingly non functional.

5” devices

Dell has shown the  Dell Mini 5, an Android based tablet running on top of a Qualcomm Snapdragon processor.

A device that is already in the market is the Archos 5 Internet Tablet which is based on Android and features an OLED display.

Set top boxes

The Quanta ebox is a slim set top box based on  Marvells Armada 510 chip

Boxee Box: The boxee box is based on the Nvidia Tegra2 and is going to be sold for below $200 by D-Link that won a best of show award at CES2010

Other touch devices

As an interesting side note, TouchRevolution showed off a 7” touch-enabled, android based platform integrated into a washing machine and a microwave

More videos can be found in my shared item feed.

A look into the (near) future

Back in the  July 2008 post i wrote:

For quite some time  i’ve argued that  the iPhone / iPod touch is right now my favourite e-reading device (see here, here and here) (Having extensively tested e-ink devices like the Iliad). Hence i drooled for a iTouch like device with a  7-9″ display.

…

IMHO, it is more likely that Apple will enter the netbook market with a typical apple twist by not doing another scaled down version of a notebook, but a device that is dedicated for optimal support of the typical tasks a netbook has to support in a home and car enviroment.: Surf and read on the web, watch video, control your home entertainment systems etc.  This device should be the best device for couch surfing as well as showing video to your kids (or let them play casual games) while being in the car.

Ever since the Newton, Apple had technology for this kind of devices and it is more or less a yearly rumour that the Newton 2.0 will finally ship. But this time i think the chances are better than ever.

We’ll see. If not , hopefully somebody uses Google’s android to build such a device.

While being wrong 2008 wrt. to the timeframe (i basically made wrong assumptions about the power consumption of  Intel ATOM and LCD displays),  i still very much believe in the scenario of an optimized device for mobile entertainment at  home (e.g couch surfing) and in car setting.

This already resonated in my “Why Times Reader 2.0 is important” post from May 2009:

For the curious: My dream eReading device has for years been an Apple media pad. Right now my specs for this device read as follows: around 1.5 pound (hopefully lighter), beefed up iPhone OS (or better dual boot, full OS at a premium price), 7 – 10” display,  wi-fi 801.11n  plus 3G, all app store goodness, bluetooth for external keyboard connectivity as well as all other bluetoothy things, plus a PixelQi multitouch display.

The exiting thing : everything except the PixelQi display is available right now, the PixelQi schedule will allow for a WWDC presentation (or a launch at the traditional september special event).

So  what i am hoping for and why?

I’ll try to do it along the lines of my introduction and the CES review.

Processor / Platform

I  think that is safe to bet that this device(s) will be the first Apple device that will incorporate some benefits of the P.A. Semi acquisition Apple made in early 2008. P.A. Semi was a fabless chip designer  specializing in low-power processor design based on ARM CPU cores. As said above all processor alternatives that i mentioned above are also based on ARM CPUs.

Since 1.5 – 2 years are a typical time frames for the the scoping of a design to a production quality chip /platform that can be mass manufactured i think we are on the safe side for that. It is also safe to assume that the platform of the tablet includes the benefits of the long term license deal with Power VR for das 2d/3D graphics as well as video de/encoding . So IMHO the paltform to be used within the table will be feature /performancewise be at least comparable to the Nvidia Tegra 2 plattform.

Displays

As argued above the display technology most likely depends on screen size of the device(s). For 5” it definitely will be AMOLED, for 7” AMOLED is a likely but pricey choice and for 10” it will be either regular LCD or a PixelQi display for the following reason:

As we have seen in the PixelQi videos above, the display seem to be ready for the market. But i remember that they said last year  that touch-enabled displays that would not suck (e.g. take away too much contrast) would be more in the June/July 2010 timeframe. So if the the tablet is going to be delayed until June lets hope that this will be the reason.

May be some of the Apple patents with regard to display technology (e.g. integrating touch and display layer in order to come up with a thinner device etc.) will be incorporated.

OS / Applications

I’m  sure that the OS will be more twisted toward  iPhoneOS  than  to Mac OS X. The main reason for that is that there definitely will be an app/content store for the device(s) and that the devices will definitely be no general purpose computers. But i’m also quite sure that the OS will be not be  identical to the current iPhoneOS. It definitely will support multi-tasking and the User interaction will be different / enhanced. It is also quite clear that there will be the possibility to pair a physical keyboard (most likely a bluetooth keyboard at least with some of the devices.

I’m also quite sure that (some) of the devices will incorporate technology / features from the Apple TV and will more or less be Apple TV 2.0.

Line Up

10” device

I think it is a fairly safe bet that the device to be unveiled on Wednesday will be a 10” tablet. And by 10” i also mean 9.7 or 10.1 ”. The device will basically have the functionality as described by Inathko and Gruber.  PixelQi display would be nice, but most likely it will be a regular LCD display.

You already can watch video stored on you’re iPhone and ipod Touch on a big screen, using either a 3rd Party Dock or a special viideo cable. Right now forwarding the signal to an external display is restricted to the playback of the video. All interaction is on the device only (which makes sense for devices like the iPhone).

This changes with the 10” tablet. As said above i expect that AppleTV functionality will be incorporated into the devices. This means that you will be either able to use  a  Front Row like interface on the device itself and / or more likely use an iPhone or iPod touch with the  Apple Remote App. I also expect a dock with gigabit network connectivity, maybe an enclosed 2.5” drive for additional content, eventually DVR and TV-Tuner capabilities and an IR port for a regular Apple Remote. This dock will eitehr come directly from Apple or from a third party provider.

5”  device

The current  ipod Touch is basically the equivalent of the 5” devices mentioned above.  Since the current Zune as well as the Nexus one are already using  AMOLED  displays i think it is a save bet that the next generation iPod touch will have an AMOLED display.  For me it is an open question if the device will have a 5” screen or if the economies of scale wil dictate that the screen is the same size as an iPhone.

May be the chosen route  is to keep the iPod Touch form factor as it is and to touch enable the successor to the iPod classic, using a greater display and a harddrive.

7”  device

Most likely either a 5” or a 7” device will be developed by Apple since there is not enough potential for diffentiating between the two devices. But may be they will go the MacBook Pro route and offer the same functionality with two different display sizes.

Set-Top Box

If Apple is interested to continue it’s Apple TV hobby, the logical consequence is to strip the 10 inch tablet of the display and use  the other parts to build a tiny and shiny Apple TV 2.0. This box can easily be sold for around $200 it may go as low as $150.

Final words

I think it is unlikely that all this devices will be introduced next week, but i would be very much surprised if at the end of the year the line-up wouldn’t more or look like sketched above.

Momentan überschlagen sich die Tweets mit Hinweisen darauf wie denn das Abendblatt auch kostenlos zu lesen ist.  Auch ich habe in meinem letzten Post darauf  hingewiesen.

Allerdings zeugt die Häme die dort zum Teil ausgeschüttet wird auch häufig von der Unkenntnis der Situation. Daher hier eine kurze Erklärung und meine Einschätzung.

Das Googleloch und das Googlebotloch sind alte Bekannte. Jeder der schon mal ernsthaft  das WallStreet Journal lesen wollte kennt zumindest das Google-Loch. Im folgenden will ich kurz erklären was die Gründe für diese Löcher sind und das das Abendblatt dies Löcher leicht stopfen könnte und es im Grunde nur eine Frage der Zeit resp. der kaufmännischen Abwägung ist ob und wann diese geschlossen werden.

Das Google-Loch und First-Click-Free

Das Google-Loch entsteht dadurch, dass die Verlage oder sonstige Content-Provider (zumindest die, die halbwegs bei Sinnen sind) nicht auf den Traffic aus der Google-Suche und Google-News verzichten wollen.

Um dies auch für Paid-Content machen zu können gibt es die First-Click-Free-Regelung von Google. Diese stellt im wesentlichen eine Ausnahme von der allgemeinen “Cloaking”-Regel dar die Aussagt, dass den Endkunden und dem Google-Crawler (der sich als googlebot identifiziert) nicht unterschiedliche Seitenversionen ausgeliefert / angezeigt werden dürfen.

Bis zum 1. Dezember besagte die First-Click-Regelung, dass dies für jeden ersten Klick, der von einer Suchergebnisseite / Google News kam, die gleiche Seite angezigt werden musste wie sie der Googlebot gesehen hat, erst Links die von dieser Seite wegführten durften dann auf Seiten führen die hinter der Paywall lagen.

Zum 1. Dezember hat Google, als eines der Zugeständnisse die sie an die Content-Provider gemacht haben, diese Regelung geändert. Seit diesem Datum gibt es die eingeschränkte First-Click-Free-Regelung die es des Content-Providern erlaubt, nach einer bestimmten Anzahl von Klicks am Tag, die von Google-Seiten kommen auch die Seite die auf diesen First-Click hin angezeigt wird hinter die Paywall zu legen. Als Minimum müssen allerdings 5 Clicks pro Tag frei sein.

Die Implementierung dieser veränderten Regelung obliegt den Verlagen (ist auch das einzig technisch sinnvolle).  Jeder der sich technisch halbwegs auskennt, weiss, das das ganze nicht trivial ist und insbesondere auch mehr Last auf den Systemen erzeugt. Daher ist es nicht verwunderlich, dass das Abendblatt die veränderte Regelung noch nicht umgesetzt hat.

Letztendlich ist aber auch eine  ökonomische Frage, ob sich der zusätzliche Aufwand überhaupt lohnt. In meiner Abwägung würde aber der Glaubwürdigkeitsaspekt überwiegen und ich gehe davon aus dass Axel-Spinger dies auch tun wird. Da Abendblatt und Berliner Morgenpost jetzt auf der gleichen technischen Plattform laufen müssen sie es ja auch nur einmal machen.

Ich gehe davon aus dass diese Lücke noch im Laufe dieses Jahres, allerspätestens im Januar geschlossen wird.

Das Googlebotloch

Eine zweite Lücke auf den in den Tweets hingewiesen wird ist das “Googlebot”-Loch. Hier gibt sich der Browser als Google-Crawler aus. Da dieser ja die Inhalte komplett sehen soll (siehe oben) wird der komplette Inhalt ausgeliefert.

Hier verwundert es mich allerdings, dass das Abendblatt diese Lücke noch nicht geschlossen hat. Das Verfahren dazu bescheibgt Google selbst auf seinen Webmaster Seiten. Es bsetht wus einem sog. Reverse DNS Lookup der feststellt ob eine IP-Addresse (die bei jedem Request mitgeliefert wird) auch aus der googlebot.com Domäne kommt, optional gefolgt von einer normalen (Forward) DNS Anfrage die dann verifiziert, ob der im ersten Schritt zurückgelieferte Name auch auf die angegebene IP-Adresse aufgelöst wird.

Dies ist notwendig, da Google nicht die IP-Adressenbereiche der Maschinen die den Crawl  ausführen bekannt gibt. Wäre das der Fall, so wäre eine Filterung der Googlebot Requests auf  diese Adressen trivial.  So ist das ganze aber mit nicht unerheblichem Aufwänden und Kosten verbunden. Darüberhinaus entstehendurch die beiden DNS-Requests Verzögerungen bei der Auslieferung der Seiten.

Im übrigen hat Google ebenfalls vor kurzem (als weiteres Zugeständnis an die Content Provider einen dedizierten Crawler-Namen für den Google News Crawler eingeführt. Dieser heisst: Googlebot-News.