Tag Archives: Android

Obligatory Nexus7 Test Post

Got my Nexus 7 a while ago,  but I wasn’t finding a use case for it. Thanks to a friend advising me to give Swiftkey a try,  I might actually make it work.
Something I might find especially useful about Swiftkey is the fact that I can mix languages,  quelque-chose que je fais assez souvent sur iOS mais qui demande un changement constant de clavier. Since I like Android’s speech recognition,  a combination of SwiftKey and speech might allow me to work efficiently.
Un truc que je remarque rapidement,  par contre,  c’est que le fait de passer d’un système à l’autre demande un certain temps de transfert de mots de passe. J’utilise des outils pour conserver des mots de passe sécuritaires,  et ils existent sur plusieurs plates-formes,  mais ça demande quand même un certain temps.
We’ll see how things go,  after a while. I do want to like Android’s and,  contrary to popular belief, I can be pretty open minded about such things. But I need appropriate contexts to try out different use cases. Otherwise,  having people yell at me because I’m yet to be sold on Android hasn’t been helpful.
Ok,  the test is enough for now. Having issues with the Swiftkey spacebar in landscape,  but I’m sure I’ll get used to it. Let’s post this and edit later.

Retour à Facebook?

Maintenant que Twitter commence à franchement m’énerver, je risque d’utiliser Facebook plus activement.

D’ailleurs, ça fait longtemps que je pense à repenser mes activités dans les médias sociaux. J’ai eu une passe un peu trop “broadcast”. J’aimerais être plus «interactif».

Faut dire que, comme la plupart des gens que je connais, je blogue presque plus. Twitter avait pris le relai, d’une certaine façon, mais seulement dans une direction. Finalement, après plusieurs années, je me rends compte que j’ai peu d’interactions sur Twitter. Sur mon compte principal, du moins.

Ce qui m’a fait remarquer tout ça, en fait, c’est d’être presque forcé de me concentrer sur une plateforme à la fois. Jusqu’à tout récemment, j’avais l’habitude d’envoyer les mêmes trucs sur plusieurs plateformes (Facebook, StatusNet, Twitter, Tumblr, LinkedIn…). Je sais bien que plusieurs personnes détestent le “crossposting”, mais c’était permis et ça me convenait.

J’utilisais le service Ping.fm, qui rendait la tâche très facile. Entre autres, il me permettait de distinguer entre des «mises à jour de statut» (“status updates”) d’envois de «microblogue». La différence était subtile et n’apparaissait pas sur toutes les plateformes, mais je la trouvais utile. Comme plusieurs le savent, mes «statuts» sont généralement bilingues, accordant une valeur particulière à la version française. C’était tout bête, comme truc, mais ça fonctionnait pour moi.

Malheureusement, Ping.fm a été acheté par Seesmic qui a été acheté par HootSuite. Par ces rachats, certaines limites ont été imposées et certaines fonctionnalités ont disparu. J’avais l’habitude d’envoyer mes trucs à plusieurs endroits à la fois, mais ça devient plus difficile à faire. Ceux qui détestent le “crossposting” seront peut-être satisfaits, mais ça m’embête un peu.

En même temps, c’est devenu plus facile de partager sur une plateforme donnée à la fois. Entre autres grâce au support natif dans OS X comme dans iOS et Android. Plusieurs «contenus» (liens et images, surtout) peuvent être envoyés directement à Facebook ou Twitter sans quitter l’application en cours d’utilisation. Pas mal. Mais ça ne facilite pas l’envoi simultané à Twitter et Facebook. Ou l’envoi sur StatusNet, Tumblr, LinkedIn, etc.

Je pensais donc à me réinvestir sur une autre plateforme.

Pourquoi Facebook? En fait, c’est pour une raison très simple: c’est sur Facebook que j’ai le plus d’interaction. Au-delà de tous les principes et de toutes les questions techniques, c’est ce qui compte le plus, pour moi. Si je suis honnête avec moi-même.

Pendant des années, j’ai essayé d’avoir le plus d’interactions possibles sur diverses plateformes. On peut dire que ma méthode était moins qu’adéquate pour toutes sortes de raisons, mais j’essayais quand même, à ma façon. La leçon que j’aurais peut-être dû apprendre, en envoyant les mêmes choses sur différentes plateformes, c’est qu’une seule d’entre ces plateformes devrait me suffire. Et c’est peut-être dommage mais cette plateforme semble être Facebook.

Pas que je vais abandonner les autres plateformes. Mais elles auront probablement un rôle différent, pour moi. Honnêtement, je suis pas certain quel rôle jouera chacune de ces plateformes. On verra à l’usage.

D’ailleurs, ç’a toujours été ma philosophie, avec mes comptes personnels: j’expérimente, je m’amuse et je vois ce qui reste. Assez différent avec des comptes organisationnels ou professionnels. Mais l’idée de base est que mon usage personnel me donne une expérience qui est utile dans le reste de ma vie.

D’ailleurs, mon compte @iethnographer sur Twitter remplit bien sa fonction. Je l’utilise peu mais, quand je l’utilise, ça «fonctionne». Pas que ça démarre des longues discussions, mais ça me permet d’avoir des interactions ciblées. C’est tout ce que je veux. D’ailleurs, les abonnés de ce compte sont généralement des gens ou des groupes avec qui j’ai des intérêts en commun. Sur mon compte perso, j’ai accumulé pas mal d’abonnés qui ont surtout un intérêt pour les médias sociaux, souvent pour des buts un peu douteux. J’ai moins de nouveaux abonnés de ce type, mais je peux pas dire que j’ai réseau bien ciblé, sur mon principal compte Twitter. Évidemment, j’aurais pu éviter cette situation, si j’avais dédié mon compte à un sujet spécifique ou si j’avais pris soin de suivre des gens avec qui j’ai des intérêts communs. J’ai fait un peu de ça de 2007 à 2008 mais, depuis, c’est devenu plus difficile.

Qu’en est-il des autres plateformes? Je vais probablement continuer à les utiliser, à l’occasion, mais je crois que c’est le moment pour moi de me «regrouper». À une certaine époque (jusqu’en 2010, disons), j’accumulais des comptes sur toutes les plateformes possibles et imaginables. Pas que je m’investissais outremesure, mais j’essayais un peu tout, je sautais dans le «chariot» (le “bandwagon”). En présentation (à PodCamp, par exemple), j’avais tendance à dire qu’on pouvait me trouver sur n’importe quelle plateforme et j’invitais les gens à me faire signe s’ils étaient sur une plateforme où je n’avais pas de présence.

Depuis environ deux ans, j’ai cessé d’ouvrir des compte sur chaque nouvelle plateforme. Pas que c’était une décision consciente de me concentrer sur celles que j’utilisais déjà. Mais j’ai arrêté de «sauter dans le train en marche». Ainsi, je n’ai pas de compte sur Pinterest, Path, App.net ou Instagram. Et je sous-utilise certains des comptes que j’ai ouverts (Branch, Diaspora, Academia.edu, Quora…). Dans le fond, j’ai pas besoin de grand-chose, pour mon usage personnel. Même pour expérimenter.

Certaines des plateformes que j’utilisais ont disparu. D’ailleurs, ce qui s’est passé avec Google Wave a eu un drôle d’effet sur moi. J’avais espoir que ça puisse devenir quelque-chose de formidable. J’ai été si amèrement déçu que ma perception de Google a pris une nouvelle tournure. D’ailleurs, parlant de Google, leur acquisition et destruction d’Aardvark (vark.com) m’a aussi perturbé. Dans toute sa simplicité, ‘Vark était devenu une super plateforme, pour moi. Si ça peut paraître bête pour certains (surtout ceux qui croient que Quora et Stack Overflow peuvent remplir les mêmes fonctions), j’ai perdu quelque-chose quand Google a étouffé l’Aardvark dans l’œuf.

Et ne parlons pas de Google Buzz.

Mais un mot quand même au sujet de Google+, qui peut être ou devenir la principale plateforme de médias sociaux, pour certains…

En fait, ces derniers temps, j’ai pensé à me concentrer sur Google+ plutôt que sur Facebook ou d’autres plateformes. Un avantage, c’est que c’est une plateforme assez polyvalente, puisqu’on peut y partager toutes sortes de choses. Puisque je dispose d’un Nexus 7, ça pourrait devenir ma plateforme privilégiée. C’est peut-être même ce qui va se passer, après un certain temps. Mais probablement pas pour le moment.

Le principal problème que j’ai, avec Google+, c’est que j’aurais besoin de m’y investir à fond pour en retirer quelque-chose d’intéressant. Pas que j’y ai pas de contacts. En fait, je suis dans plus de cercles G+ que je n’ai d’«amis» sur Facebook. Mais ces contacts G+ demandent un autre type d’attention que ce que je suis disposé à accorder. Et, j’insiste, c’est une question qualitative, pas quantitative. Je parle pas d’un effort accru mais d’un effort distinct.

Parce qu’utiliser G+, pour moi, ça entre pas dans ma routine.

Pas que ce que j’y envoie tombe dans le vide. Proportionnellement, j’y reçois presqu’autant de retours que sur mon compte Twitter personnel. Et ces interactions sont tout-à-fait valables, dans le contexte. Mais elles sont d’un certain type, lié à ceux de mes contacts qui participent à une certaine sphère technologique. Pour rendre la plateforme vraiment satisfaisante, ça me demanderait un boulot de fond. Je devrais changer ma façon de procéder, provoquer de nouveaux types d’interactions, me lier à des gens qui partagent d’autres types d’intérêts, «produire du contenu» d’un certain type, etc.

Faut dire qu’il manque certains trucs, à Google+ (qui a pourtant fait son apparition il y a un an et demi). Par exemple, je peux pas envoyer des trucs sur G+ à partir d’autres plateformes, y compris WordPress et Foursquare. Je peux archiver mes envois grâce à ThinkUp, mais ça demeure bien limité. Pas vraiment de façon d’explorer les recoins de mon réseau social au-delà du premier degré. Pas vraiment de «groupes de discussion», non plus. Et les profils sont aussi limités que ceux de Google Profiles.

En disant tout ça, je continue à réfléchir (c’est un peu pour ça que j’écris). Peut-être que G+ deviendra bientôt ma plateforme de choix, surtout si j’arrive à me convaincre que les obstacles sont «dans ma tête». Un peu comme ma décision de «donner une chance à Android» (plutôt insatisfaisant), j’essaie non seulement de garder l’esprit ouvert mais de faire quelques efforts vers d’autres façons de fonctionner.

Un problème particulier, c’est que Google+ m’inspire pas. Je vois mal ce que ça peut devenir. J’y vois pas d’avantage majeur par rapport à Twitter et Facebook, malgré la réputation de Google dans certains de mes cercles d’amis. Bien que je sois sensible au discours sur l’ouverture et que le comportement corporatif de Facebook et Twitter puisse laisser à désirer, j’ai encore rien vu dans Google+ qui peut ouvrir des nouvelles possibilités, pour moi. Et les beaux principes qui semblent avantager Google dans les yeux de certains n’ont que peu de valeur à mes yeux quand ils sont associés à une entreprise qui, à la fois, accorde si peu d’importance à l’être humain et se concentre tellement sur la publicité.

En passant, je comprends bien que G+ est bien plus qu’une plateforme de média social. Mais je pense ici à mes activités dans les médias sociaux, pas aux objectifs que Google s’est fixé. Je trouve que l’engin de recherche Google continue à se détériorer et G+ n’a pas eu d’effet bien positif de ce côté. Je pense même qu’il y a une méprise fondamentale sur le type d’activité qui rend les médias sociaux si intéressants.

Ce qui me pousse à concentrer certaines de mes activités de médias sociaux sur Facebook.

Depuis sept ans que je suis sur Facebook, j’ai pu observer beaucoup de changements. Plusieurs de ces changements ont un effet négatif sur l’expérience générale de la plateforme. Mais certains sont assez utiles, pour moi.

En 2005, mes seuls contacts Facebook étaient quelques-uns des étudiants avec lesquels j’étais en contact, aux États-Unis, y compris certains de ceux qui suivaient mes cours, à Bridgewater. Par la suite, j’ai eu quelques contacts Facebook dans des universités canadiennes. Mais c’est seulement  au moment où la plateforme a été ouverte à tout le monde que mon réseau sur Facebook a pris son sens.

Il y a aussi eu la période des applications. Plusieurs d’entre elles causaient plus de frustration que de nouveaux usages, mais elles ont poussé les gens à investir plus de temps sur Facebook, ce qui a eu certains effets intéressants sur l’utilisation de la plateforme. Ce que plusieurs ont bien compris, c’est qu’une fois que les gens sont sur une plateforme, ils risquent d’y passer plus de temps. Même avant les jeux sur Facebook (Spymaster, d’abord, puis FarmVille et autres phénomènes de masse), les applications ont eu pour effet d’asseoir la plateforme sur une base plus solide.

Dans les autres développements plutôt utiles, il y a eu l’ajout de «flux d’actualités» (“newsfeeds”) et l’amélioration du système de messagerie. J’ai jamais été très fort sur le clavardage alors le système hybride que Facebook propose tend à me convenir relativement bien.

Évidemment, il y a des tas de trucs qui me fatiguent, avec Facebook. Mais, finalement, c’est moins problématique que ça l’était, à une certaine époque.

Donc, on verra bien ce qui va se passer. Disons simplement que je vais retourner à Facebook avec un esprit ouvert.

 

Early iPhone Rumours

[The Lar.me/2ke link originally pointed to Mike Davidson’s 2005 piece. More explanations here.]

[Update, a bit later… Added some thoughts, links, and tags…]

While listening to the Critical Path podcast on 5by5 with Asymco’s Horace Dediu, I got stuck on Dediu’s comment that there weren’t iPhone rumours when Google acquired Android. After a quick search, I ended up on this 2005 piece by Mike Davidson (written eight months before the Google purchase), so I tweeted to @Asymco with a link to Davidson’s post. Several people, including Dediu himself, tell me that this wouldn’t qualify as a rumour (though my own definition of rumour probably differs from theirs). Still, I’ve received some comments about how insightful this piece was. It was partly based on a November 2004 piece by Russell Beattie, which was itself a partial reaction to a short Ross Mayfield post about a “WiFi iPod”. In comments on Davidson’s piece, Ste Grainer mentioned a Robert X. Cringely piece about a Mac Media Centre.

I later found a NYT piece from 2002 which contained an actual rumour about the “iPhone”, including the name:

industry analysts see evidence that Apple is contemplating what inside the company is being called an ”iPhone.”

This, I think, would qualify as a rumour in most people’s definitions, though it didn’t include “leaked prototypes”.

But back to this Davidson piece, which might have been more insightful than the NYT’s one or even Beattie’s…

In hindsight, Davidson’s piece was both prescient of what would actually happen and telling in what didn’t happen. He talked about satellite radio, Plays for Sure, and WiMAX none of which panned out as planned. Also, Davidson surmised some things about Apple’s “content play” which were both less ambitious and more impactful (on Apple’s bottomline) than what actually happened. Apple’s 2007 move against DRM might have been surprising to the 2005 Davidson. And it’s funny to think back to an era when high prices for flash storage made it prohibitive to build a mobile device… ;-)

Basically, though, Davidson was speculating about an integrated device which would replace several devices at once:

It won’t be long before the cell phone is your camera, your music player, your organizer, your portable web client, your remote control, and your digital wallet

[We could argue about Android’s NFC play being closer to the digital wallet ideal than Apple’s passbook. The other parts are closer to a Treo anyway…]

In the abstract at least (and in Steve Jobs’s way of describing it), the iPhone has been this integrated communicating device about which people had been talking for years. So, kudos to Mike Davidson for predicting this a while in advance. He was neither the first nor the last, but he painted an interesting portrait.

Now, there are other parts to this story, I think. Given the fact that work on what would become iOS devices (iPad first, we’re told) hadn’t begun when Charles Wolf told the New York Times about a device called “iPhone” internally at Apple, I get the impression that the rumours predated much of the actual development work leading to the device. Speculation happened later still. It seems to relate to a number of things demonstrated by STS generally and SCOT specifically. Namely that technological development is embedded in a broader social process.

I also find interesting some side notions in all of these pieces. For instance, ideas about the impact the device might have on people’s usage. Or the fact that the move from the Treo to the iPhone ends up being quite significant, in retrospect. Even Davidson’s points about headphones and retail stores seem to relate to current things. So does the existence of the iPod touch and Apple TV in Apple’s lineup, addressing Mayfield and Cringely, respectively.

I also end up reflecting upon the shift from the “digital hub” strategy (peaking around 2007 or so) to the one revealed with iCloud, “Back to the Mac” and, yes, even Apple Maps. Dediu devotes much time to his mentor Clay Christensen’s notion of “disruptive innovation” and spent part of this latest Critcal Path episode talking about the risks behind Apple not being disruptive enough.

All of this makes me think…

Not that I have a very clear idea of what might happen but, recently, I’ve been thinking about the broader picture. Including the Maps kerfuffle. The importance of social disruption. Apple’s financial state and market presence. The so-called “Post-PC” era in relation to other “post-” notions (post-industrialism, post-colonialism, post-nationalism, post-modernism…). The boring nature of the Google/Apple conflict. The recent financial crisis. The tech world’s emphasis on Apple. The future of academia and education. The iconicity of Steve Jobs…

As Mike Wesch has been saying:

We’ll need to rethink a few things…

iCloud Dreams

Got lots more to blog, including something about “received knowledge”. And a list of things I love about Google. (I’m also getting started on “logical punctuation”, as you may already be noticing…)

But, at the risk of attracting trolls and Apple haters, I thought I’d post some notes from a daydreaming session. In some ways, it’s easier to write than the rest. And it’s more “time-sensitive”, in that my thoughts will likely sound very silly, very soon.

But I don’t care.

So, yes, this post is about iCloud, which will be officially unveiled in a few hours. No, it doesn’t mean that I expect anything specific from iCloud or that I trust Apple to deliver something awesome.

Contrary to what some people seem to think, I’m no Apple fanboi. I use a number of Apple products and I find several of them to be close to the ideal in my workflow, but I don’t have any sort of deep involvement in “the Cult of Mac”, Apple Inc., AAPL, or even Apple-focused development. I use the tools and like them, but I don’t think Apple will save us any more than will Facebook, Dell, Google, Amazon, Twitter, HP, or Microsoft.

[Automattic, on the other hand;-) ]

So, back to iCloud…

According to many, “cloud computing” (whatever that means) is a domain in which Apple has been relatively weak. I tend to share that opinion, despite the fact that a number of tools that I use have to do with either “the cloud”, Apple, or both. What might give trolls and haters some ammo is that I do have a MobileMe subscription. But there’s a lot I dislike about it and the only features I really find valuable are “over-the-air” syncing (henceforth “OTA”) and “Find My iPhone”. And since I use GSync on my iPod touch, MobileMe’s OTA isn’t that incredibly important. Depending on what iCloud may be, my MobileMe renewal (which comes up in a few days) could be a very hard sell. I don’t regret having it as it did help me retrieve my iPad. But it’s rather expensive if it’s the only thing it does. (Then again, so is insurance of any kind, but I digress…)

So, I’m no MobileMe poweruser. Why would I care about iCloud?

In some ways, I don’t. Or, at least, I didn’t. Until very recently, though I saw rumours about Apple’s new “cloud services”, I was only vaguely intrigued about it. I did think that it might solve my MobileMe issue. But I treated these rumours with a lot of skepticism and a rather low level of interest.

Yet, today, iCloud has been giving me a drift-off moment. Like Android did, at some point.

It’s not that I have predictions to make about iCloud. I’m not even speculating, really. But it got me to think. And, I admit, I enjoy thinking.

Without further ado (about nothing), my fanciful thoughts stemming from a short daydreaming session about iCloud…

The main thing people seem to be expecting  (based on rumoured negotiations with music publishers) is a music streaming service similar to Music Beta by Google or a digital file storage service similar to Amazon Cloud Drive. Both of these are quite neat and I could see myself using something like this. But it’s not exactly what makes me dream. While iTunes integration might make Apple’s version of a music streaming service somewhat more useful than the others. Besides, rumours have it that, through agreements with the recording industry, iCloud might sync music without requiring long uploads. It’s quite possible that this only works with tracks purchased on iTunes, which would upset those whose expectations are high, but could already be useful to some.

Where I’m beginning to drift off, though, is when I start thinking about OTA for podcasts. It’s been high up on my wishlist, as a feature, and you might say that it’s a pet peeve with iOS devices for podcatching. Having to sync my iPod touch to my main desktop just to have my podcast list up-to-date is a major hassle. Sure, there are apps which sync podcasts OTA. Problem is, they can’t add podcasts to the native iOS media player, which is a dealbreaker in my case. (As absurd as it may sound to others, one reason this is a dealbreaker is that I now listen to everything at doublespeed. Hey, it’s my podcast library and I listen to it as I want, ok?)

So, OTA podcasts would constitute a significant enhancement to my experience. Nothing absolutely required and possibly not that significant for others, but it’d really help me in more ways than one could imagine.

Thing is, syncing my iPod touch isn’t just about podcasts, even though podcatching is my main motivation to sync. After all, I don’t listen to podcasts yet I still sync my iPad. So, what else? Well, backing up is the main other thing, and it might be one of the core reason for Apple’s implicit insistence on syncing. That’d be classic Apple. Data loss can be such a big problem that they’d “do what they can” to prevent users from losing data. Far from perfect, in my experience (I ended up having some problems when I lost my “iTunes Library” file). And quite annoying when it meant that the sync would take a very long time to finish at precisely the point when I’m trying to leave home. But a classic Apple move, even in the way Apple haters may mean it.

So OTA synchronization of the whole iOS device, and not just podcasts or music, would be a definite plus, in this perspective. If it does end up coming with iCloud, it’d provide support to the idea that the tethering of iOS devices to desktop computers is really about ensuring that users back up their devices…

…and stay up to date. Firmware updates aren’t that frequent, but they’re probably a major part of the equation for Apple.

But not so much for me. If OTA podcasts were available, I’d still sync my iOS devices on occasion, through whatever means necessary. In fact, were I to use an Android device, a backup app would be essential, to me. So still not much dreaming from the backup aspect of iCloud.

Although… Sync is much broader than preventing device-specific data loss and making sure your device has the latest firmware.

For one thing, it does encompass some of the aforementioned OTA functionalities in MobileMe. Useful, but still not dreamworthy.

We get a bit closer to a “dream come true” if we talk about Xmarks, a bookmark-sync service originally meant for Firefox.  Sure, it sounds incredibly prosaic. But OTA bookmarks would open up a wide range of possibilities. This is about a qualitative difference from going OTA. In the case of backups, it’s about avoiding an annoyance but, arguably, it’s not really about changing something major about our behaviour. (Then again, maybe it is, with people who don’t back their devices up.) Point is, with something as simple as bookmarks, OTA is “disruptive”. At least, it gets me to daydream. One reason is that:

…no matter how fundamental they have been for the Web, links and bookmarks have yet to find their full value.

Hmm… Ok, perhaps a bit hyperbolic… So let me rephrase…

There’s still a lot to be done with URLs and, as simple as they are, I love thinking about links. Maybe I’m just obsessed with URLs.

As it so happens, I have a full list of thoughts about “link processing” and I’ve already blogged about related topics (on more than one occasion, in different contexts, going back to relatively early blogposts). And I even think social science can help.

I mean, think about it! There’s so much you can do, with links! Much of it is obvious, but I’d argue, rarely discussed. For instance, it’s very clear that we can post links pretty much anywhere. Doing so, we’re sharing their “content”. (In a semiotic sense, links are indices. I wish we can move from the “semantic Web” to the “semiotic Web”. But that’s another issue.) Sharing a link is the basic act of the social Web. It’s so obvious and frequent that it seems not to require discussion”.

Another obvious thing about links: we can measure the number of times they’re followed. In 2011, more than thirty years after hypertext has been introduced as a stable concept, much of the Web’s finances still relies on “clickthroughs”. Seems important.

And there’s a lot of processing which can be done with URLs: shortening them, adding them to “to do” lists, checking them for validity, keeping them in link libraries, archiving their “content”, showing them as external or internal links, preventing them from “rotting away”, showing the wordcount or reading time of the item they “target”, display them as QR codes, abuse them, etc.

As you can notice, it’s easy to get me on a tangent simply thinking about URLs. What’s this have t’do with iCloud, you ask? Probably not much, in terms of the actual service which will be announced at Moscone. But I’ve been dreaming about iCloud as a way to integrate Diigo, Instapaper, Delicious, reddit, digg, Slashdot, StumbleUpon, Spurl, The NethernetXmarks

Hey, I told you I was dreaming! Something as simple as managing, processing, sharing, and archiving links in iCloud could lead to just about anything, in my imagination.

And speaking of Xmarks… It’s now owned by Lastpass, a company which focus on password management. IMHO, some Lastpass-like features could make their way in diverse products, including iCloud. Is this far-fetched? Possibly. But secure handling of passwords can be a major issue in both of Apple’s new operating systems (Mac OS X Lion and iOS5). From “keychains” to SSO, there’s a lot of work to be done which relates to password management, in my mind.

Which leads me to think about authentication in general and the rumours about “deep Twitter integration in iOS 5”. (Not directly related to iCloud, but who knows?) Again, something which can send me (and others) on drift-off moments. What if this integration suddenly made iOS devices more useful in terms of social networking services? Something to ponder, if one has a propensity for pondering.

At the same time, given the relative lack of activity on iTunes Ping, I wouldn’t bet on Twitter integration having that major an impact by itself. Not unlike Google, Apple has a hard time making a mark on the social Web. Now, if Twitter integration does connect to everything else Apple does, it could lead to interesting things. A full-fledged online identity? Access to contacts for not only messaging and photo sharing but for collaboration, group management, and media sharing? Not betting on any of this, but it could be fun. Again, not specific to iCloud, but quite related to “The Cloud”. If Twitter integration is deep enough, in iOS 5, it’d be possible to use iOS devices for “cloud computing”, getting further into the “post-PC era”.

An iCloud feature which is expected by several people, is something like an OTA version of the “iTunes file sharing” feature in iOS. Several apps (especially Apple’s own apps) use iTunes and a USB cable to share files. It was a welcome addition to iTunes 9.1 but it’s rather inconvenient. So many other apps rely on Dropbox for file sharing.

Which leads me to dream about iCloud as a replacement for Dropbox. Sounds extremely unlikely that it’ll have the full Dropbox feature set, especially if one thinks about the “Pro 50” and “Pro 100” plans on Dropbox. But I dream of the day when Apple’s iDisk will compete with Dropbox. Not that I’m convinced it ever will. But it’d make Apple’s devices all the more useful if it did.

Something similar, which isn’t frequently discussed directly, in connection with iCloud rumours, but which would rock: Mozy- or Carbonite-style backup, for Mac OS X machines. Sounds very unlikely that Apple will ever offer something like this but, as crazy as it may sound, the connection between Time Capsule and iCloud would be great if it went that far. From a user’s perspective, the similarities between Time Machine backup and “backing up in the cloud” (à la Mozy/Carbonite) are quite obvious. The advantages of both are clear. And while no hardware announcement is supposed to make its way to the WWDC 2011 keynote, I’d give the Time Capsule some consideration if it provided me with the equivalent of what I currently have with Mozy. Not to mention that Mozy has already sparked some drift-off moments, in me, before they announced their new plans. What if I could have a single service which combines features from Mozy, Time Machine, Dropbox, and YouSendIt?

I even think about the possibilities in terms of web hosting. As it stands, MobileMe does allow for some Web publishing through the iWeb application in its iLife suite. But iWeb has never been a major effort for Apple and it hasn’t been seen a significant update in quite a while. What if iCloud could become a true webhost just like, say… iWeb.com? (Semi-disclaimer: I won a free account with iWeb.com, last Fall, and I host some sites there. I also know some of the people who work there…)

Yet again, I don’t expect this to happen. It’s not speculation, on my part. It’s a daydream.

The reason this makes me dream is that I find all these things to be related and I wish they were integrated more seamlessly. Something about which Apple haters may not care much is the type of integration represented by iTunes. As clunky as iTunes may be, in some respects, it’s quite a success in terms of integrating a lot of different things. In fact, it probably overextended its reach a bit too much and we need to replace it. Apple needs to replace iTunes and we should also replace iTunes in our lives.

Like Gruber, I end up thinking about iCloud in relation to iTunes more than in relation to MobileMe. But I also dream about the ideal cloud service, which would not only sync and backup files between iOS devices, hundreds of millions of iTunes store accounts, and Macs, but replace several of the services for which I’m paying monthly fees.

Here’s to dreaming…

Other parts of this crazy, iCloud-infused daydream, in notes form:

Handhelds for the Rest of Us?

Ok, it probably shouldn’t become part of my habits but this is another repost of a blog comment motivated by the OLPC XO.

This time, it’s a reply to Niti Bhan’s enthusiastic blogpost about the eeePC: Perspective 2.0: The little eeePC that could has become the real “iPod” of personal computing

This time, I’m heavily editing my comments. So it’s less of a repost than a new blogpost. In some ways, it’s partly a follow-up to my “Ultimate Handheld Device” post (which ended up focusing on spatial positioning).

Given the OLPC context, the angle here is, hopefully, a culturally aware version of “a handheld device for the rest of us.”

Here goes…

I think there’s room in the World for a device category more similar to handhelds than to subnotebooks. Let’s call it “handhelds for the rest of us” (HftRoU). Something between a cellphone, a portable gaming console, a portable media player, and a personal digital assistant. Handheld devices exist which cover most of these features/applications, but I’m mostly using this categorization to think about the future of handhelds in a globalised World.

The “new” device category could serve as the inspiration for a follow-up to the OLPC project. One thing about which I keep thinking, in relation to the “OLPC” project, is that the ‘L’ part was too restrictive. Sure, laptops can be great tools for students, especially if these students are used to (or need to be trained in) working with and typing long-form text. But I don’t think that laptops represent the most “disruptive technology” around. If we think about their global penetration and widespread impact, cellphones are much closer to the leapfrog effect about which we all have been writing.

So, why not just talk about a cellphone or smartphone? Well, I’m trying to think both more broadly and more specifically. Cellphones are already helping people empower themselves. The next step might to add selected features which bring them closer to the OLPC dream. Also, since cellphones are widely distributed already, I think it’s important to think about devices which may complement cellphones. I have some ideas about non-handheld tools which could make cellphones even more relevant in people’s lives. But they will have to wait for another blogpost.

So, to put it simply, “handhelds for the rest of us” (HftRoU) are somewhere between the OLPC XO-1 and Apple’s original iPhone, in terms of features. In terms of prices, I dream that it could be closer to that of basic cellphones which are in the hands of so many people across the globe. I don’t know what that price may be but I heard things which sounded like a third of the price the OLPC originally had in mind (so, a sixth of the current price). Sure, it may take a while before such a low cost can be reached. But I actually don’t think we’re in a hurry.

I guess I’m just thinking of the electronics (and global) version of the Ford T. With more solidarity in mind. And cultural awareness.

Google’s Open Handset Alliance (OHA) may produce something more appropriate to “global contexts” than Apple’s iPhone. In comparison with Apple’s iPhone, devices developed by the OHA could be better adapted to the cultural, climatic, and economic conditions of those people who don’t have easy access to the kind of computers “we” take for granted. At the very least, the OHA has good representation on at least three continents and, like the old OLPC project, the OHA is officially dedicated to openness.

I actually care fairly little about which teams will develop devices in this category. In fact, I hope that new manufacturers will spring up in some local communities and that major manufacturers will pay attention.

I don’t care about who does it, I’m mostly interested in what the devices will make possible. Learning, broadly speaking. Communicating, in different ways. Empowering themselves, generally.

One thing I have in mind, and which deviates from the OLPC mission, is that there should be appropriate handheld devices for all age-ranges. I do understand the focus on 6-12 year-olds the old OLPC had. But I don’t think it’s very productive to only sell devices to that age-range. Especially not in those parts of the world (i.e., almost anywhere) where generation gaps don’t imply that children are isolated from adults. In fact, as an anthropologist, I react rather strongly to the thought that children should be the exclusive target of a project meant to empower people. But I digress, as always.

I don’t tend to be a feature-freak but I have been thinking about the main features the prototypical device in this category should have. It’s not a rigid set of guidelines. It’s just a way to think out loud about technology’s integration in human life.

The OS and GUI, which seem like major advantages of the eeePC, could certainly be of the mobile/handheld type instead of the desktop/laptop type. The usual suspects: Symbian, NewtonOS, Android, Zune, PalmOS, Cocoa Touch, embedded Linux, Playstation Portable, WindowsCE, and Nintendo DS. At a certain level of abstraction, there are so many commonalities between all of these that it doesn’t seem very efficient to invent a completely new GUI/OS “paradigm,” like OLPC’s Sugar was apparently trying to do.

The HftRoU require some form of networking or wireless connectivity feature. WiFi (802.11*), GSM, UMTS, WiMAX, Bluetooth… Doesn’t need to be extremely fast, but it should be flexible and it absolutely cannot be cost-prohibitive. IP might make much more sense than, say, SMS/MMS, but a lot can be done with any kind of data transmission between devices. XO-style mesh networking could be a very interesting option. As VoIP has proven, voice can efficiently be transmitted as data so “voice networks” aren’t necessary.

My sense is that a multitouch interface with an accelerometer would be extremely effective. Yes, I’m thinking of Apple’s Touch devices and MacBooks. As well as about the Microsoft Surface, and Jeff Han’s Perceptive Pixel. One thing all of these have shown is how “intuitive” it can be to interact with a machine using gestures. Haptic feedback could also be useful but I’m not convinced it’s “there yet.”

I’m really not sure a keyboard is very important. In fact, I think that keyboard-focused laptops and tablets are the wrong basis for thinking about “handhelds for the rest of us.” Bear in mind that I’m not thinking about devices for would-be office workers or even programmers. I’m thinking about the broadest user base you can imagine. “The Rest of Us” in the sense of, those not already using computers very directly. And that user base isn’t that invested in (or committed to) touch-typing. Even people who are very literate don’t tend to be extremely efficient typists. If we think about global literacy rates, typing might be one thing which needs to be leapfrogged. After all, a cellphone keypad can be quite effective in some hands and there are several other ways to input text, especially if typing isn’t too ingrained in you. Furthermore, keyboards aren’t that convenient in multilingual contexts (i.e., in most parts of the world). I say: avoid the keyboard altogether, make it available as an option, or use a virtual one. People will complain. But it’s a necessary step.

If the device is to be used for voice communication, some audio support is absolutely required. Even if voice communication isn’t part of it (and I’m not completely convinced it’s the one required feature), audio is very useful, IMHO (I’m an aural guy). In some parts of the world, speakers are much favoured over headphones or headsets. But I personally wish that at least some HftRoU could have external audio inputs/outputs. Maybe through USB or an iPod-style connector.

A voice interface would be fabulous, but there still seem to be technical issues with both speech recognition and speech synthesis. I used to work in that field and I keep dreaming, like Bill Gates and others do, that speech will finally take the world by storm. But maybe the time still hasn’t come.

It’s hard to tell what size the screen should be. There probably needs to be a range of devices with varying screen sizes. Apple’s Touch devices prove that you don’t need a very large screen to have an immersive experience. Maybe some HftRoU screens should in fact be larger than that of an iPhone or iPod touch. Especially if people are to read or write long-form text on them. Maybe the eeePC had it right. Especially if the devices’ form factor is more like a big handheld than like a small subnotebook (i.e., slimmer than an eeePC). One reason form factor matters, in my mind, is that it could make the devices “disappear.” That, and the difference between having a device on you (in your pocket) and carrying a bag with a device in it. Form factor was a big issue with my Newton MessagePad 130. As the OLPC XO showed, cost and power consumption are also important issues regarding screen size. I’d vote for a range of screens between 3.5 inch (iPhone) and 8.9 inch (eeePC 900) with a rather high resolution. A multitouch version of the XO’s screen could be a major contribution.

In terms of both audio and screen features, some consideration should be given to adaptive technologies. Most of us take for granted that “almost anyone” can hear and see. We usually don’t perceive major issues in the fact that “personal computing” typically focuses on visual and auditory stimuli. But if these devices truly are “for the rest of us,” they could help empower visually- or hearing-impaired individuals, who are often marginalized. This is especially relevant in the logic of humanitarianism.

HftRoU needs a much autonomy from a power source as possible. Both in terms of the number of hours devices can be operated without needing to be connected to a power source and in terms of flexibility in power sources. Power management is a major technological issue, with portable, handheld, and mobile devices. Engineers are hard at work, trying to find as many solutions to this issue as they can. This was, obviously, a major area of research for the OLPC. But I’m not even sure the solutions they have found are the only relevant ones for what I imagine HftRoU to be.

GPS could have interesting uses, but doesn’t seem very cost-effective. Other “wireless positioning systems” (à la Skyhook) might reprsent a more rational option. Still, I think positioning systems are one of the next big things. Not only for navigation or for location-based targeting. But for a set of “unintended uses” which are the hallmark of truly disruptive technology. I still remember an article (probably in the venerable Wired magazine) about the use of GPS/GIS for research into climate change. Such “unintended uses” are, in my mind, much closer to the constructionist ideal than the OLPC XO’s unified design can ever get.

Though a camera seems to be a given in any portable or mobile device (even the OLPC XO has one), I’m not yet that clear on how important it really is. Sure, people like taking pictures or filming things. Yes, pictures taken through cellphones have had a lasting impact on social and cultural events. But I still get the feeling that the main reason cameras are included on so many devices is for impulse buying, not as a feature to be used so frequently by all users. Also, standalone cameras probably have a rather high level of penetration already and it might be best not to duplicate this type of feature. But, of course, a camera could easily be a differentiating factor between two devices in the same category. I don’t think that cameras should be absent from HftRoU. I just think it’s possible to have “killer apps” without cameras. Again, I’m biased.

Apart from networking/connectivity uses, Bluetooth seems like a luxury. Sure, it can be neat. But I don’t feel it adds that much functionality to HftRoU. Yet again, I could be proven wrong. Especially if networking and other inter-device communication are combined. At some abstract level, there isn’t that much difference between exchanging data across a network and controlling a device with another device.

Yes, I do realize I pretty much described an iPod touch (or an iPhone without camera, Bluetooth, or cellphone fees). I’ve been lusting over an iPod touch since September and it does colour my approach. I sincerely think the iPod touch could serve as an inspiration for a new device type. But, again, I care very little about which company makes that device. I don’t even care about how open the operating system is.

As long as our minds are open.

Android "Sales Pitch" and "Drift-Off"

(Google’s Android is an open software platform to be put on cellphones next year.)

There’s something to this video. Something imilar to Steve Jobs’s alleged “Reality Distortion Field,” but possibly less connected to presentation skills or perceived charisma. Though Mike seems to be a more experienced presenter than those we see in other videos about Android, and though the presentation format is much slicker than other videos about Android, there’s something special about this video, to me.

For one thing, the content of the three “Androidology” videos are easy to understand, even for a non-developer/non-coder. Sure, you need to know some basic terms. But the broad concepts are easy to understand, at least for those who have been observing the field of technology. One interesting thing about this is that these “Androidology” videos are explicitly meant for software programmers. The “you” in this context specifically refers to would-be developers of Android applications. At the same time, these videos do a better job, IMHO, of “selling Android to tech gurus” than other Android-related videos published by Google.

Now, I do find this specific video quite interesting, and my interest has to do with a specific meaning of “sales pitch.”

I keep going back to a Wired article about the “drift-off moment” during sales pitches (or demos):

When Mann gives a demo, what he’s waiting for is what salespeople call “the drift-off moment.” The client’s eyes get gooey, and they’re staring into space. They’re not bored – they’re imagining what they could do with SurveyBuilder. All tech salespeople mention this – they’ve succeeded not when they rivet the client’s attention, but when they lose it.

I apply this to teaching when I can and I specifically talked about this during a presentation about online tools for teaching.

This video on four of Android’s APIs had this effect on me. Despite not being a developer myself, I started imagining what people could do with Android. It was just a few brief moments. But very effective.

The four APIs discussed in this video are (in presentation order):

  1. Location Manager
  2. XMPP Service
  3. Notification Manager
  4. View System (including MapView and WebView)

Mike’s concise (!) explanations on all of these are quite straightforward (though I was still unclear on XMPP and on details of the three other APIs after watching the video). Yet something “clicked” in my mind while watching this. Sure, it might just be serendipitous. But there’s something about these APIs or about the way they are described which make me daydream.

Which is exactly what the “drift-off moment” is all about.

Technorati Tags: , , , , , , , , , , , , , , , , ,