Category Archives: techno lust

Body and Tech: My Year in Quantified Self

Though I’m a qual, I started quantifying my self a year ago.

Not Even Started Yet

This post is long. You’ve been warned.

This post is about my experience with the Quantified Self (QuantSelf). As such, it may sound quite enthusiastic, as my perspective on my own selfquantification is optimistic. I do have several issues with the Quantified Self notion generally and with the technology associated with selfquantification. Those issues will have to wait until a future blogpost.

While I realize QuantSelf is broader than fitness/wellness/health tracking, my own selfquantification experience focuses on working with my body to improve my health. My future posts on the Quantified Self would probably address the rest more specifically.

You might notice that I frequently link to the DC Rainmaker site, which is a remarkably invaluable source of information and insight about a number of things related to fitness and fitness technology. Honestly, I don’t know how this guy does it. He’s a one-man shop for everything related to sports and fitness gadgets.

Though many QuantSelf devices are already available on the market, very few of them are available in Quebec. On occasion, I think about getting one shipped to someone I know in the US and then manage to pick it up in person, get a friend to bring it to Montreal, or get it reshipped. If there were such a thing as the ideal QuantSelf device, for me, I might do so.

(The title of this post refers to the song Body and Soul, and I perceive something of a broader shift in the mind/body dualism, even leading to post- and transhumanism. But this post is more about my own self.)

Quaint Quant

I can be quite skeptical of quantitative data. Not that quants aren’t adept at telling us very convincing things. But numbers tend to hide many issues, when used improperly. People who are well-versed in quantitative analysis can do fascinating things, leading to genuine insight. But many other people use numbers as a way to “prove” diverse things, sometimes remaining oblivious to methodological and epistemological issues with quantification.

Still, I have been accumulating fairly large amounts of quantitative data about my self. Especially about somatic dimensions of my self.

Started with this a while ago, but it’s really in January 2013 that my Quantified Self ways took prominence in my life.

Start Counting

It all started with the Wahoo Fitness fisica key and soft heartrate strap. Bought those years ago (April 2011), after thinking about it for months (December 2010).

Had tried different exercise/workout/fitness regimens over the years, but kept getting worried about possible negative effects. For instance, some of the exercises I’d try in a gym would quickly send my heart racing to the top of my healthy range. Though, in the past, I had been in a more decent shape than people might have surmised, I was in bad enough shape at that point that it was better for me to exercise caution while exercising.

At least, that’s the summary of what happened which might make sense to a number of people. Though I was severely overweight for most of my life, I had long periods of time during which I was able to run up long flights of stairs without getting out of breath. This has changed in the past several years, along with other health issues. The other health issues are much more draining and they may not be related to weight, but weight is the part on which people tend to focus, because it’s so visible. For instance, doctors who meet me for a few minutes, only once, will spend more time talking about weight than a legitimate health concern I have. It’s easy for me to lose weight, but I wanted to do it in the best possible way. Cavalier attitudes are discouraging.

Habits, Old and New

Something I like about my (in this case not-so-sorry) self is that I can effortlessly train myself into new habits. I’m exactly the opposite of someone who’d get hooked on almost anything. I never smoked or took drugs, so I’ve never had to kick one of those trickiest of habits. But I often stop drinking coffee or alcohol with no issue whatsoever. Case in point: I’m fairly well-known as a coffee geek yet I drank less than two full cups of coffee during the last two months.

Getting new habits is as easy for me as kicking new ones. Not that it’s perfect, of course. I occasionally forget to bring down the lid on the toilet seat. But if I put my mind to something, I can usually undertake it. Willpower, intrinsic motivation, and selfdiscipline are among my strengths.

My health is a significant part of this. What I started a year ago is an exercise and fitness habit that I’ve been able to maintain and might keep up for a while, if I decide to do so.

Part of it is a Pilates-infused yoga habit that I brought to my life last January and which became a daily routine in February or March. As is the case with other things in my life, I was able to add this routine to my life after getting encouragement from experts. In this case, yoga and Pilates instructors. Though it may be less impressive than other things I’ve done, this routine has clearly had a tremendous impact on my life.

Spoiler alert: I also took on a workout schedule with an exercise bike. Biked 2015 miles between January 16, 2013 and January 15, 2014.

But I’m getting ahead of myself.

So Close, Yet So Far

Flashback to March, 2011. Long before I really got into QuantSelf.

At the time, I had the motivation to get back into shape, but I had to find a way to do it safely. The fact that I didn’t have access to a family physician played a part in that.

So I got the Wahoo key, a dongle which allows an iOS device to connect to ANT+ equipment, such as heartrate straps (including the one I bought at the same time as the key). Which means that I was able to track my heartrate during exercise using my iPod touch and iPad (I later got an iPhone).

Used that setup on occasion. Including at the gym. Worked fairly well as a way to keep track of my workouts, but I had some difficulty fitting gym workouts in my schedule. Not only does it take a lot of time to go to a gym (even one connected to my office by a tunnel), but my other health issues made it very difficult to do any kind of exercise for several hours after any meal. In fact, those other health issues made most exercise very unpleasant. I understand the notion of pushing your limits, getting out of your comfort zone. I’m fine with some types of discomfort and I don’t feel the need to prove to anyone that I can push my limits. But the kind of discomfort I’m talking about was more discouraging than anything else. For one thing, I wasn’t feeling anything pleasant at any point during or after exercising.

So, although I had some equipment to keep track of my workouts, I wasn’t working out on that regular a basis.

I know, typical, right? But that’s before I really started in QuantSelf.

Baby Steps

In the meantime (November, 2011), I got a Jawbone UP wristband. First generation.

That device was my first real foray into “Quantified Self”, as it’s normally understood. It allowed me to track my steps and my sleep. Something about this felt good. Turns out that, under normal circumstances, my stepcount can be fairly decent, which is in itself encouraging. And connecting to this type of data had the effect of helping me notice some correlations between my activity and my energy levels. There have been times when I’ve felt like I hadn’t walked much and then noticed that I had been fairly active. And vice-versa. I wasn’t getting into such data that intensely, but I had started accumulating some data on my steps.

Gotta start somewhere.

Sleepwalking

My sleep was more interesting, as I was noticing some difficult nights. An encouraging thing, to me, is that it usually doesn’t take me much time to get to sleep (about 10 minutes, according to the UP). Neat stuff, but not earth-shattering.

Obviously, the UP stopped working. Got refunded, and all, but it was still “a bummer”. My experience with the first generation UP had given me a taste of QuantSelf, but the whole thing was inconclusive.

Feeling Pressure

Fastforward to late December, 2012 and early January, 2013. The holiday break was a very difficult time for me, physically. I was getting all sorts of issues, compounding one another. One of them was a series of intense headaches. I had been getting those on occasion since Summer, 2011. By late 2012, my headaches were becoming more frequent and longer-lasting. On occasion, physicians at walk-in clinics had told me that my headaches probably had to do with blood pressure and they had encouraged me to take my pressure at the pharmacy, once in a while. While my pressure had been normal-to-optimal (110/80) for a large part of my life, it was becoming clear that my blood pressure had increased and was occasionally getting into more dangerous territory. So I eventually decided to buy a bloodpressure monitor.

Which became my first selfquantification method. Since my bloodpressure monitor is a basic no-frills model, it doesn’t sync to anything or send data anywhere. But I started manually tracking my bloodpressure by taking pictures and putting the data in a spreadsheet. Because the monitor often gives me different readings (especially depending on which arm I got them from), I would input lowest and highest readings from each arm in my spreadsheet.

Tensio

My first bloodpressure reading, that first evening (January 3, 2013), was enough of a concern that a nurse at Quebec’s phone health consultation service recommended that I consult with a physician at yet another walk-in clinic. (Can you tell not having a family physician was an issue? I eventually got one, but that’s another post.) Not that it was an emergency, but it was a good idea to take this seriously.

So, on January 4, 2013, I went to meet Dr. Anthony Rizzuto, a general practitioner at a walk-in clinic in my neighbourhood.

Getting Attention

At the clinic, I was diagnosed with hypertension (high bloodpressure). Though that health issue was less troublesome to me than the rest, it got me the attention of that physician who gave me exactly the right kind of support. Thanks to that doctor, a bit of medication, and all sorts of efforts on my part, that issue was soon under control and I’m clearly out of the woods on this one. I’ve documented the whole thing in my previous blogpost. Summary version of that post (it’s in French, after all): more than extrinsic motivation, the right kind of encouragement can make all the difference in the world. (In all honesty, I already had all the intrinsic motivation I needed. No worries there!)

Really, that bloodpressure issue wasn’t that big of a deal. Sure, it got me a bit worried, especially about risks of getting a stroke. But I had been more worried and discouraged by other health issues, so that bloodpressure issue wasn’t the main thing. The fact that hypertension got me medical attention is the best part, though. Some things I was unable to do on my own. I needed encouragement, of course, but I also needed professional advice. More specifically, I felt that I needed a green light. A license to exercise.

Y’know how, in the US especially, “they” keep saying that you should “consult a physician” before doing strenuous exercise? Y’know, the fine print on exercise programs, fitness tools, and the like? Though I don’t live in the US anymore and we don’t have the same litigation culture here, I took that admonition to heart. So I was hesitant to take on a full fitness/training/exercise routine before I could consult with a physician. I didn’t have a family doctor, so it was difficult.

But, a year ago, I got the medical attention I needed. Since we’re not in the US, questions about the possibility to undertake exercise are met with some surprise. Still, I was able to get “approval” on doing more exercise. In fact, exercise was part of a solution to the hypertension issue which had brought this (minimal level of) medical attention to my case.

So I got exactly what I needed. A nod from a licensed medical practitioner. “Go ahead.”

Weight, Weight! Don’t Tell Me![1]

Something I got soon after visiting the clinic was a scale. More specifically, I got a Conair WW54C Weight Watchers Body Analysis Digital Precision Scale. I would weigh myself everyday (more than once a day, in fact) and write down the measures for total weight, body water percentage, and body fat percentage. As with the bloodpressure monitor, I was doing this by hand, since my scale wasn’t connected in any way to another device or to a network.

Weighing My Options

I eventually bought a second scale, a Starfrit iFit. That one is even more basic than the Weight Watchers scale, as it doesn’t do any “body analysis” beyond weight. But having two scales makes me much more confident about the readings I get. For reasons I don’t fully understand, I keep getting significant discrepancies in my readings. On a given scale, I would weigh myself three times and keep the average. The delta between the highest and lowest readings on that same scale would often be 200g or half a pound. The delta between the two scales can be as much as 500g or over one pound. Unfortunately, these discrepancies aren’t regular: it’s not that one scale is offset from the other by a certain amount. One day, the Weight Watchers has the highest readings and the Starfrit has the highest readings. I try to position myself the same way on each scale every time and I think both of them are on as flat a surface as I can get. But I keep getting different readings. I was writing down averages from both scales in my spreadsheet. As I often weighed myself more than once a day and would get a total of six readings every time, that was a significant amount of time spent on getting the most basic of data.

Food for Thought

At the same time, I started tracking my calories intake. I had done so in the past, including with the USDA National Nutrient Database on PalmOS devices (along with the Eat Watch app from the Hacker’s Diet). Things have improved quite a bit since that time. Not that tracking calories has become effortless, far from it. It’s still a chore, an ordeal, a pain in the neck, and possibly a relatively bad idea. Still, it’s now easier to input food items in a database which provides extensive nutritional data on most items. Because these databases are partly crowdsourced, it’s possible to add values for items which are specific to Canada, for instance. It’s also become easier to get nutritional values for diverse items online, including meals at restaurant chains. Though I don’t tend to eat at chain restaurants, tracking my calories encouraged me to do so, however insidiously.

But I digress.

Nutritional data also became part of my QuantSelf spreadsheet. Along with data from my bloodpressure monitor and body composition scale, I would copy nutritional values (protein, fat, sodium, carbohydrates…) from a database. At one point, I even started calculating my estimated and actual weightloss in that spreadsheet. Before doing so, I needed to know my calories expenditure.

Zipping

One of the first things I got besides the bloodpressure monitor and scale(s) was a fitbit Zip. Two months earlier (November, 2012), I had bought a fitbit One. But I lost it. The Zip was less expensive and, though it lacks some of the One’s features (tracking elevation, for instance), it was good enough for my needs at the time.

In fact, I prefer the Zip over the One, mostly because it uses a coin battery, so it doesn’t need to be recharged. I’ve been carrying it for a year and my fitbit profile has some useful data about my activity. Sure, it’s just a “glorified pedometer”. But the glorification is welcomed, as regular synchronization over Bluetooth is very useful a feature. My Zip isn’t a big deal, for me. It’s as much of a part of my life as my glasses, though I wear it more often (including during my sleep, though it doesn’t track sleep data).

Stepping UP

I also bought a new Jawbone UP. Yep, despite issues I had with the first generation one. Unfortunately, the UP isn’t really that much more reliable now than it was at the time. But they keep replacing it. A couple or weeks ago, my UP stopped working and I got a replacement. I think it’s the fifth one.

Despite its unreliability, I really like the UP for its sleeptracking and “gentle waking” features. If it hadn’t been for the UP, I probably wouldn’t have realized the importance of sleep as deeply as I have. In other words, the encouragement to sleep more is something I didn’t realize I needed. Plus, it’s really neat to wake up to a gentle buzz, at an appropriate point in my sleep cycle. I probably wouldn’t have gotten the UP just for this, but it’s something I miss every time my UP stops working. And there’s been several of those times.

My favourite among UP’s features is one they added, through firmware, after a while (though it might have been in the current UP from the start). It’s the ability to take “smart naps”. Meaning that I can set an alarm to wake me up after a certain time or after I’ve slept a certain amount of time. The way I set it up, I can take a 20 minute nap and I’ll be awaken by the UP after a maximum of 35 minutes. Without this alarm, I’d oversleep and likely feel more messed up after the nap than before. The alarm is also reassuring in that it makes the nap fit neatly my schedule. I don’t nap everyday, but naps are one of these underrated things I feel could be discussed more. Especially when it comes to heavy work sessions such as writing reports or grading papers. My life might shift radically in the near future and it’s quite possible that naps will be erased from my workweek indefinitely. But chances are that my workweek will also become much more manageable once I stop freelancing.

The UP also notifies me when I’ve been inactive for a certain duration (say, 45 minutes). It only does so a few times a month, on average, because I don’t tend to be that inactive. Exceptions are during long stretches of writing, so it’s a useful reminder to take a break. In fact, the UP just buzzed while I was writing this post so I should go and do my routine.

(It’s fun to write on my iPad while working out. Although, I tend to remain in the aerobic/endurance or even in the fitness/fatburning zone. I should still reach mile 2100 during this workout.)

Contrary to the fitbit Zip, the UP does require a charge on a regular basis. In fact, it seems that the battery is a large part of the reliability issue. So, after a while, I got into the habit of plugging my UP to the wall during my daily yoga/Pilates routine. My routine usually takes over half an hour and the UP is usually charged after 20 minutes.

Back UP

It may seem strange to have two activity trackers with complete feature overlap (there’s nothing the fitbit Zip does that the Jawbone UP doesn’t do). I probably wouldn’t have planned it this way, had I been able to get a Jawbone UP right at first. If I were to do it now, I might get a different device from either fitbit or Jawbone (the Nike+ FuelBand is offputting, to me).

I do find it useful to have two activity trackers. For one thing, the UP is unreliable enough that the Zip is useful as a backup. The Zip also stopped working once, so there’s been six periods of time during the past year during which I only had one fitness tracker. Having two trackers means that there’s no hiatus in my tracking, which has a significant impact in the routine aspect of selfquantification. Chances are slim that I would have completely given up on QuantSelf during such a hiatus. But I would probably have been less encouraged by selfquantification had I been forced to depend on one device.

Having two devices also helps me get a more accurate picture of my activities. Though the Zip and UP allegedly track the same steps, there’s usually some discrepancy between the two, as is fairly common among activity trackers. For some reasons, the discrepancy has actually decreased after a few months (and after I adapted my UP usage to my workout). But it’s useful to have two sources of data points.

Especially when I do an actual workout.

Been Working Out, Haven’t You?

In January, last year, I also bought an exercise bike, for use in my apartment. I know, sounds like a cliché, right? Getting an exercise bike after New Year? Well, it wasn’t a New Year’s resolution but, had it been one, I could be proud to say I kept it (my hypothetical resolution; I know, weird structure; you get what I mean, right?).

Right away, I started doing bike workouts on a very regular basis. From three to five times a week, during most weeks. Contrary to going to a gym, exercising at home is easy to fit in my freelancing schedule. I almost always work out before breakfast, so there’s no digestion issue involved. Since I’m by myself, it means I feel no pressure or judgment from others, a very significant factor in my case. Though I’m an extrovert’s extrovert (86 percentile), gyms are really offputting, to me. Because of my bodyshape, age, and overall appearance, I really feel like I don’t “fit”. It does depend on the gym, and I had a fairly good time at UMoncton’s Ceps back in 2003. But ConU’s gym wasn’t a place where I enjoyed working out.

My home workouts have become a fun part of my week. Not that the effort level is low, but I often do different things while working out, including listen to podcasts and music, reading, and even writing. As many people know, music can be very encouraging during a workout. So can a podcast, as it takes your attention elsewhere and you might accomplish more than you thought, during a podcast. Same thing with reading and writing, and I wrote part of this post while working out.

Sure, I could do most of this in a gym. The convenience factor at home is just too high, though. I can have as many things as I want by my sides, on a table and on a chair, so I just have to reach out when I need any of them. Apart from headphones, a music playing device, and a towel (all things I’d have at a gym) I typically have the following items with me when I do a home workout:

  • Travel mug full of tea
  • Stainless steel water bottle full of herbal tea (proper tea is theft)
  • Britta bottle full of water (I do drink a lot of fluid while working out)
  • three mobile devices (iPhone, iPad, Nexus 7)
  • Small weights,
  • Reading glasses
  • Squeeze balls

Wouldn’t be so easy to bring all of that to a gym. Not to mention that I can wear whatever I want, listen to whatever I want, and make whatever noise I want (I occasionally yell beats to music, as it’s fun and encouraging). I know some athletic people prefer gym workouts over home ones. I’m not athletic. And I know what I prefer.

On Track

Since this post is nominally about QuantSelf, how do I track my workouts, you ask? Well, it turns out that my Zip and UP do help me track them out, though in different ways. To get the UP to track my bike workouts, I have to put it around one of my pedals, a trick which took me a while to figure out.

2014-01-22 18.38.24

The Zip tracks my workouts from its usual position but it often counts way fewer “steps” than the UP does. So that’s one level of tracking. My workouts are part of my stepcounts for the days during which I do them.

Putting My Heart into IT

More importantly, though, my bike workouts have made my heartrate strap very useful. By pairing the strap with Digifit’s iBiker app, I get continuous heartrate monitoring, with full heartrate chart, notifications about “zones” (such as “fat burning”, “aerobic”, and “anaerobic”), and a recovery mode which lets me know how quickly my heartrate decreases after the workout. (I could also control the music app, but I tend to listen to Rdio instead.) The main reason I chose iBiker is that it works natively on the iPad. Early on, I decided I’d use my iPad to track my workouts because the battery lasts longer than on an iPhone or iPod touch, and the large display accommodates more information. The charts iBiker produces are quite neat and all the data can be synced to Digifit’s cloud service, which also syncs with my account on the fitbit cloud service (notice how everything has a cloud service?).

20140103-162048.jpg

Heartrate monitoring is close to essential, for workouts. Sure, it’d be possible to do exercise without it. But the difference it makes is more significant than one might imagine. It’s one of those things that one may only grok after trying it. Since I’m able to monitor my heartrate in realtime, I’m able to pace myself, to manage my exertion. By looking at the chart in realtime, I can tell how long I’ve spent at which intensity level and can decide to remain in a “zone” for as long as I want. Continuous feedback means that I can experiment with adjustment to the workout’s effort level, by pedaling faster or increasing tension. It’s also encouraging to notice that I need increasing intensity levels to reach higher heartrates, since my physical condition has been improving tremendously over the past year. I really value any encouragement I can get.

Now, I know it’s possible to get continuous heartrate monitoring on gym equipment. But I’ve noticed in the past that this monitoring wasn’t that reliable as I would often lose the heartrate signal, probably because of perspiration. On equipment I’ve tried, it wasn’t possible to see a graphical representation of my heartrate through the whole workout so, although I knew my current heartrate, I couldn’t really tell how long I was maintaining it. Not to mention that it wasn’t possible to sync that data to anything. Even though some of that equipment can allegedly be used with a special key to transfer data to a computer, that key wasn’t available.

It’d also be possible to do continuous heartrate monitoring with a “fitness watch”. A big issue with most of these is that data cannot be transferred to another device. Several of the new “wearable devices” do add this functionality. But these devices are quite expensive and, as far as I can see in most in-depth reviews, not necessarily that reliable. Besides, their displays are so small that it’d be impossible to get as complete a heartrate chart as the one I get on iBiker. I got pretty excited about the Neptune Pine, though, and I feel sad I had to cancel my pledge at the very last minute (for financial reasons). Sounds like it can become a rather neat device.

As should be obvious, by now, the bike I got (Marcy Recumbent Mag Cycle ME–709 from Impex) is a no-frills one. It was among the least expensive exercise bikes I’ve seen but it was also one with high ratings on Amazon. It’s as basic as you can get and I’ve been looking into upgrading. But other exercise bikes aren’t that significantly improved over this one. I don’t currently have enough money to buy a highend bike, but money isn’t the only issue. What I’d really like to get is exercise equipment which can be paired with another device, especially a tablet. Have yet to see an exercise bike, rower, treadmill, or elliptical which does. At any price. Sure, I could eventually find ways to hack things together to get more communication between my devices, but that’d be a lot of work for little results. For instance, it might be possible to find a cadence sensor which works on an exercise bike (or tweak one to make it work), thereby giving some indication of pace/speed and distance. However, I doubt that there’s exercise equipment which would allow a tablet to control tension/strength/difficulty. It’d be so neat if it were available. Obviously, it’s far from a requirement. But none of the QuantSelf stuff is required to have a good time while exercising.

Off the Bike

I use iBiker and my heartrate monitor during other activities besides bike workouts. Despite its name, iBiker supports several activity types (including walking and hiking) and has a category for “Other” activities. I occasionally use iBiker on my iPhone when I go on a walk for fitness reasons. Brisk walks do seem to help me in my fitness regime, but I tend to focus on bike workouts instead. I already walk a fair bit and much of that walking is relatively intense, so I feel less of a need to do it as an exercise, these days. And I rarely have my heartrate strap with me when I decide to take a walk. At some point, I had bought a Garmin footpod and kept installing it on shoes I was wearing. I did use it on occasion, including during a trip to Europe (June–July, 2012). It tends to require a bit of time to successfully pair with a mobile app, but it works as advertised. Yet, I haven’t really been quantifying my walks in the same way, so it hasn’t been as useful as I had wished.

More frequently, I use iBiker and my heartrate strap during my yoga/Pilates routine. “Do you really get your heart running fast enough to make it worthwhile”, you ask? No, but that’s kind of the point. Apart from a few peaks, my heartrate charts during such a routine tends to remain in Zone 0, or “Warmup/Cooldown”. The peaks are interesting because they correspond to a few moves and poses which do feel a bit harder (such as pushups or even the plank pose). That, to me, is valuable information and I kind of wish I could see which moves and poses I’ve done for how long using some QuantSelf tool. I even thought about filming myself, but I would then need to label each pose or move by hand, something I’d be very unlikely to do more than once or twice. It sounds like the Atlas might be used in such a way, as it’s supposed to recognize different activities, including custom ones. Not only is it not available, yet, but it’s so targeted at the high performance fitness training niche that I don’t think it could work for me.

One thing I’ve noticed from my iBiker-tracked routine is that my resting heartrate has gone down very significantly. As with my recovery and the amount of effort necessary to increase my heartrate, I interpret this as a positive sign. With other indicators, I could get a fuller picture of my routine’s effectiveness. I mean, I feel its tremendous effectiveness in diverse ways, including sensations I’d have a hard time explaining (such as an “opening of the lungs” and a capacity to kill discomfort in three breaths). The increase in my flexibility is something I could almost measure. But I don’t really have tools to fully quantify my yoga routine. That might be a good thing.

Another situation in which I’ve worn my heartrate strap is… while sleeping. Again, the idea here is clearly not to measure how many calories I burn or to monitor how “strenuous” sleeping can be as an exercise. But it’s interesting to pair the sleep data from my UP with some data from my heart during sleep. Even there, the decrease in my heartrate is quite significant, which signals to me a large improvement in the quality of my sleep. Last summer (July, 2013), I tracked a night during which my average heartrate was actually within Zone 1. More recently (November, 2013), my sleeping heartrate was below my resting heartrate, as it should be.

Using the Wahoo key on those occasions can be quite inconvenient. When I was using it to track my brisk walks, I would frequently lose signal, as the dongle was disconnecting from my iPad or iPhone. For some reason, I would also lose signal while sleeping (though the dongle would remain unmoved).

So I eventually bought a Blue HR, from Wahoo, to replace the key+strap combination. Instead of ANT+, the Blue HR uses Bluetooth LE to connect directly with a phone or tablet, without any need for a dongle. I bought it in part because of the frequent disconnections with the Wahoo key. I rarely had those problems during bike exercises, but I thought having a more reliable signal might encourage me to track my activities. I also thought I might be able to pair the Blue HR with a version of iBiker running on my Nexus 7 (first generation). It doesn’t seem to work and I think the Nexus 7 doesn’t support Bluetooth LE. I was also able to hand down my ANT+ setup (Wahoo key, heartrate strap, and footpod) to someone who might find it useful as a way to track walks. We’ll see how that goes.

‘Figures!

Going back to my QuantSelf spreadsheet. iBiker, Zip, and UP all output counts of burnt calories. Since Digifit iBiker syncs with my fitbit account, I’ve been using the fitbit number.

Inputting that number in the spreadsheet meant that I was able to measure how many extra calories I had burnt as compared to calories I had ingested. That number then allowed me to evaluate how much weight I had lost on a given day. For a while, my average was around 135g, but I had stretches of quicker weightloss (to the point that I was almost scolded by a doctor after losing too much weight in too little time). Something which struck me is that, despite the imprecision of so many things in that spreadsheet, the evaluated weightloss and actual loss of weight were remarkably similar. Not that there was perfect synchronization between the two, as it takes a bit of time to see the results of burning more calories. But I was able to predict my weight with surprising accuracy, and pinpoint patterns in some of the discrepancies. There was a kind of cycle by which the actual number would trail the predicted one, for a few days. My guess is that it had to do with something like water retention and I tried adjusting from the lowest figure (when I seem to be the least hydrated) and the highest one (when I seem to retain the most water in my body).

Obsessed, Much?

ObsessiveSpreadsheet

As is clear to almost anyone, this was getting rather obsessive. Which is the reason I’ve used the past tense with many of these statements. I basically don’t use my QuantSelf spreadsheet, anymore. One reason is that (in March, 2013) I was advised by a healthcare professional (a nutrition specialist) to stop counting my calories intake and focus on eating until I’m satiated while ramping up my exercise, a bit (in intensity, while decreasing frequency). It was probably good advice, but it did have a somewhat discouraging effect. I agree that the whole process had become excessive and that it wasn’t really sustainable. But what replaced it was, for a while, not that useful. It’s only in November, 2013 that a nutritionist/dietician was able to give me useful advice to complement what I had been given. My current approach is much better than any other approach I’ve used, in large part because it allows me to control some of my digestive issues.

So stopping the calories-focused monitoring was a great idea. I eventually stopped updating most columns in my spreadsheet.

What I kept writing down was the set of readings from my two “dumb” scales.

Scaling Up

Abandoning my spreadsheet didn’t imply that I had stopped selfquantifying.

In fact, I stepped up my QuantSelf a bit, about a month ago (December, 2013) by getting a Withings WS–50 Smart Body Analyzer. That WiFi-enabled scale is practically the prototype of QuantSelf and Internet of Things devices. More than I had imagined, it’s “just the thing I needed” in my selfquantified life.

The main advantage it has over my Weight Watchers scale is that it syncs data with my Withings cloud service account. That’s significant because the automated data collection saves me from my obsessive spreadsheet while letting me learn about my weightloss progression. Bingo!

Sure, I could do the same thing by hand, adding my scale readings to any of my other accounts. Not only would it be a chore to do so, but it’d encourage me to dig too deep in those figures. I learnt a lot during my obsessive phase, but I don’t need to go back to that mode. There are many approaches in between that excessive data collection and letting Withings do the work. I don’t even need to explore those intermediary approaches.

There are other things to like about the Withings scale. One is Position Control™, which does seem to increase the accuracy of the measurements. Its weight-tracking graphs (app and Web) are quite reassuring, as they show clear trends, between disparate datapoints. WithingsWeightKg WithingsLeanMassPercent

This Withings scale also measures heartrate, something I find less useful given my usage of a continuous heartrate monitor. Finally, it has sensors for air temperature and CO2 levels, which are features I’d expect in a (pre-Google) Nest product.

Though it does measure body fat percentage, the Withings Smart Body Analyzer doesn’t measure water percentage or bone mass, contrary to my low-end Weight Watchers body composition scale. Funnily enough, it’s around the time I got the Withings that I finally started gaining enough muscle mass to be able to notice the shift on the Weight Watchers. Prior to that, including during my excessive phase, my body fat and body water percentages added up to a very stable number. I would occasionally notice fluctuations of ~0.1%, but no downward trend. I did notice trends in my overall condition when the body water percentage was a bit higher, but it never went very high. Since late November or early December, those percentages started changing for the first time. My body fat percentage decreased by almost 2%, my body water percentage increased by more than 1%, and the total of the two decreased by 0.6%. Since these percentages are now stable and I have other indicators going in the same direction, I think this improvement in fat vs. water is real and my muscle mass did start to increase a bit (contrary to what a friend said can happen with people our age). It may not sound like much but I’ll take whatever encouragement I get, especially in such a short amount of time.

The Ideal QuantSelf Device

On his The Talk Show podcast, Gruber has been dismissing the craze in QuantSelf and fitness devices, qualifying them as a solved problem. I know what he means, but I gather his experience differs from mine.

I feel we’re in the “Rio Volt era” of the QuantSelf story.

The Rio Volt was one of the first CD players which could read MP3 files. I got one, at the time, and it was a significant piece of my music listening experience. I started ripping many of my CDs and creating fairly large compilations that I could bring with me as I traveled. I had a carrying case for the Volt and about 12 CDs, which means that I could carry about 8GB of music (or about 140 hours at the 128kbps bitrate which was so common at the time). Quite a bit less than my whole CD collection (about 150GB), but a whole lot more than what I was used to. As I was traveling and moving frequently, at the time, the Volt helped me get into rather… excessive music listening habits. Maybe not excessive compared to a contemporary teenager in terms of time, but music listening had become quite important to me, at a time when I wasn’t playing music as frequently as before.

There have been many other music players before, during, and after the Rio Volt. The one which really changed things was probably… the Microsoft Zune? Nah, just kidding. The iRiver players were much cooler (I had an iRiver H–120 which I used as a really neat fieldrecording device). Some people might argue that things really took a turn when Apple released the iPod. Dunno about that, I’m no Apple fanboi.

Regardless of which MP3-playing device was most prominent, it’s probably clear to most people that music players have changed a lot since the days of the Creative Nomad and the Rio Volt. Some of these changes could possibly have been predicted, at the time. But I’m convinced that very few people understood the implications of those changes.

Current QuantSelf devices don’t appear very crude. And they’re certainly quite diverse. CES2014 was the site of a number of announcements, demos, and releases having to do with QuantSelf, fitness, Internet of Things, and wearable devices (unsurprisingly, DC Rainmaker has a useful two-part roundup). But despite my interest in some of these devices, I really don’t think we’ve reached the real breakthrough with those devices.

In terms of fitness/wellness/health devices, specifically, I sometimes daydream about features or featuresets. For instance, I really wish a given device would combine the key features of some existing devices, as in the case of body water measurements and the Withings Smart Body Analyzer. A “killer feature”, for me, would be strapless continuous 24/7 heartrate monitoring which could be standalone (keeping the data without transmitting it) yet able to sync data with other devices for display and analysis, and which would work at rest as well as during workouts, underwater as well as in dry contexts.

Some devices (including the Basis B1 and Mio Alpha) seem to come close to this, but they all have little flaws, imperfections, tradeoffs. At an engineering level, it should be an interesting problem so I fully expect that we’ll at least see an incremental evolution from the current state of the market. Some devices measure body temperature and perspiration. These can be useful indicators of activity level and might help one gain insight about other aspects of the physical self. I happen to perspire profusely, so I’d be interested in that kind of data. As is often the case, unexpected usage of such tools could prove very innovative.

How about a device which does some blood analysis, making it easier to gain data on nutrients or cholesterol levels? I often think about the risks of selfdiagnosis and selfmedication. Those issues, related to QuantSelf, will probably come in a future post.

I also daydream about something deeper, though more imprecise. More than a featureset or a “killer feature”, I’m thinking about the potential for QuantSelf as a whole. Yes, I also think about many tricky issues around selfquantification. But I perceive something interesting going on with some of these devices. Some affordances of Quantified Self technology. Including the connections this technology can have with other technologies and domains, including tablets and smartphones, patient-focused medicine, Internet of Things, prosumption, “wearable hubs”, crowdsourced research, 3D printing, postindustrialization, and technological appropriation. These are my issues, in the sense that they’re things about which I care and think. I don’t necessarily mean issues as problems or worries, but things which either give me pause or get me to discuss with others.

Much of this will come in later posts, I guess. Including a series of issues I have with self-quantification, expanded from some of the things I’ve alluded to, here.

Walkthrough

These lines are separated from many of the preceding ones (I don’t write linearly) by a relatively brisk walk from a café to my place. Even without any QuantSelf device, I have quite a bit of data about this walk. For instance, I know it took me 40 minutes because I checked the time before and after. According to Google Maps, it’s between 4,1km and 4,2km from that café to my place, depending on which path one might take (I took an alternative route, but it’s probably close to the Google Maps directions, in terms of distance). It’s also supposed to be a 50 minute walk, so I feel fairly good about my pace (encouraging!). I also know it’s –20°C, outside (–28°C with windchill, according to one source). I could probably get some data about elevation, which might be interesting (I’d say about half of that walk was going up).

With two of my QuantSelf devices (UP and Zip), I get even more data. For instance, I can tell how many steps I took (it looks like it’s close to 5k, but I could get a more precise figure). I also realize the intensity of this activity, as both devices show that I started at a moderate pace followed by an intense pace for most of the duration. These devices also include this walk in measuring calories burnt (2.1Mcal according to UP, 2.7Mcal according to Zip), distance walked (11.2km according to Zip, 12.3km according to UP), active minutes (117’ Zip, 149’ UP), and stepcount (16.4k UP, 15.7k Zip). Not too shabby, considering that it’s still early evening as I write these lines.

2014-01-21 18.47.54 2014-01-21 18.47.48 2014-01-21 18.46.47

Since I didn’t have my heartrate monitor on me and didn’t specifically track this activity, there’s a fair bit of data I don’t have. For instance, I don’t know which part was most strenuous. And I don’t know how quickly I recovered. If I don’t note it down, it’s difficult to compare this activity to other activities. I might remember more or less which streets I took, but I’d need to map it myself. These are all things I could have gotten from a fitness app coupled with my heartrate monitor.

As is the case with cameras, the best QuantSelf device is the one you have with you.

I’m glad I have data about this walk. Chances are I would have taken public transit had it not been for my QuantSelf devices. There weren’t that many people walking across the Mont-Royal park, by this weather.

Would I get fitter more efficiently if I had the ideal tool for selfquantification? I doubt it.

Besides, I’m not in that much of a hurry.


  1. Don’t like my puns? Well, it’s my blogpost and I’ll cry if I want to.  ↩

Wearable Hub: Getting the Ball Rolling

Statement

After years of hype, wearable devices are happening. What wearable computing lacks is a way to integrate devices into a broader system.

Disclaimer/Disclosure/Warning

  • For the past two months or so, I’ve been taking notes about this “wearable hub” idea (started around CES’s time, as wearable devices like the Pebble and Google Glass were discussed with more intensity). At this point, I have over 3000 words in notes, which probably means that I’d have enough material for a long essay. This post is just a way to release a few ideas and to “think aloud” about what wearables may mean.
  • Some of these notes have to do with the fact that I started using a few wearable devices to monitor my activities, after a health issue pushed me to start doing some exercise.
  • I’m not a technologist nor do I play one on this blog. I’m primarily an ethnographer, with diverse interests in technology and its implications for human beings. I do research on technological appropriation and some of the course I teach relate to the social dimensions of technology. Some of the approaches to technology that I discuss in those courses relate to constructionism and Actor-Network Theory.
  • I consider myself a “geek ethnographer” in the sense that I take part in geek culture (and have come out as a geek) but I’m also an outsider to geekdom.
  • Contrary to the likes of McLuhan, Carr, and Morozov, my perspective on technology and society is non-deterministic. The way I use them, “implication” and “affordance” aren’t about causal effects or, even, about direct connections. I’m not saying that society is causing technology to appear nor am I proposing a line from tools to social impacts. Technology and society are in a complex system.
  • Further, my approach isn’t predictive. I’m not saying what will happen based on technological advances nor am I saying what technology will appear. I’m thinking about the meaning of technology in an intersubjective way.
  • My personal attitude on tools and gadgets is rather ambivalent. This becomes clear as I go back and forth between techno-enthusiastic contexts (where I can almost appear like a Luddite) and techno-skeptical contexts (where some might label me as a gadget freak). I integrate a number of tools in my life but I can be quite wary about them.
  • I’m not wedded to the ideas I’m putting forth, here. They’re just broad musings of what might be. More than anything, I hope to generate thoughtful discussion. That’s why I start this post with a broad statement (not my usual style).
  • Of course, I know that other people have had similar ideas and I know that a concept of “wearable hub” already exists. It’s obvious enough that it’s one of these things which can be invented independently.

From Wearables to Hubs

Back in the 1990s, “wearable computing” became something of a futuristic buzzword, often having to do with articles of clothing. There have been many experiments and prototypes converging on an idea that we would, one day, be able to wear something resembling a full computer. Meanwhile, “personal digital assistants” became something of a niche product and embedded systems became an important dimension of car manufacturing.

Fast-forward to 2007, when a significant shift in the use of smartphones occurred. Smartphones existed before that time, but their usages, meanings, and positions in the public discourse changed quite radically around the time of the iPhone’s release. Not that the iPhone itself “caused a smartphone revolution” or that smartphone adoption suddenly reached a “tipping point”. I conceive of this shift as a complex interplay between society and tools. Not only more Kuhn than Popper, but more Latour than Kurzweil.

Smartphones, it may be argued, “happened”.

Without being described as “wearable devices”, smartphones started playing some of the functions people might have assigned to wearable devices. The move was subtle enough that Limor Fried recently described it as a realization she’s been having. Some tech enthusiasts may be designing location-aware purses and heads-up displays in the form of glasses. Smartphones are already doing a lot of the things wearables were supposed to do. Many people “wear” smartphones at most times during their waking lives and these Internet-connected devices are full of sensors. With the proliferation of cases, one might even perceive some of them as fashion accessories, like watches and sunglasses.

Where smartphones become more interesting, in terms of wearable computing, is as de facto wearable hubs.

My Wearable Devices

Which brings me to mention the four sensors I’ve been using more extensively during the past two months:

Yes, these all have to do with fitness (and there’s quite a bit of overlap between them). And, yes, I started using them a few days after the New Year. But it’s not about holiday gifts or New Year’s resolutions. I’ve had some of these devices for a while and decided to use them after consulting with a physician about hypertension. Not only have they helped me quite a bit in solving some health issues, but these devices got me to think.

(I carry several other things with me at most times. Some of my favourites include Tenqa REMXD Bluetooth headphones and the LiveScribe echo smartpen.)

One aspect is that they’re all about the so-called “quantified self”. As a qualitative researcher, I tend to be skeptical of quants. In this case, though, the stats I’m collecting about myself fit with my qualitative approach. Along with quantitative data from these devices, I’ve started collecting qualitative data about my life. The next step is to integrate all those data points automatically.

These sensors are also connected to “gamification”, a tendency I find worrisome, preferring playfulness. Though game mechanics are applied to the use of these sensors, I choose to rely on my intrinsic motivation, not paying much attention to scores and badges.

But the part which pushed me to start taking the most notes was that all these sensors connect with my iOS ()and Android) devices. And this is where the “wearable hub” comes into play. None of these devices is autonomous. They’re all part of my personal “arsenal”, the equipment I have on my me on most occasions. Though there are many similarities between them, they still serve different purposes, which are much more limited than those “wearable computers” might have been expected to serve. Without a central device serving as a type of “hub”, these sensors wouldn’t be very useful. This “hub” needs not be a smartphone, despite the fact that, by default, smartphones are taken to be the key piece in this kind of setup.

In my personal scenario, I do use a smartphone as a hub. But I also use tablets. And I could easily use an existing device of another type (say, an iPod touch), or even a new type of device meant to serve as a wearable hub. Smartphones’ “hub” affordances aren’t exclusive.

From Digital Hub to Wearable Hub

Most of the devices which would likely serve as hubs for wearable sensors can be described as “Post-PC”. They’re clearly “personal” and they’re arguably “computers”. Yet they’re significantly different from the “Personal Computers” which have been so important at the end of last century (desktop and laptop computers not used as servers, regardless of the OS they run).

Wearability is a key point, here. But it’s not just a matter of weight or form factor. A wearable hub needs to be wireless in at least two important ways: independent from a power source and connected to other devices through radio waves. The fact that they’re worn at all times also implies a certain degree of integration with other things carried throughout the day (wallets, purses, backpacks, pockets…). These devices may also be more “personal” than PCs because they may be more apparent and more amenable to customization than PCs.

Smartphones fit the bill as wearable hubs. Their form factors and battery life make them wearable enough. Bluetooth (or ANT+, Nike+, etc.) has been used to pair them wirelessly with sensors. Their connectivity to GPS and cellular networking as well as their audio and visual i/o can have interesting uses (mapping a walk, data updates during a commute, voice feedback…). And though they’re far from ubiquitous, smartphones have become quite common in key markets.

Part of the reason I keep thinking about “hubs” has to do with comments made in 2001 by then Apple CEO Steve Jobs about the “digital lifestyle” age in “PC evolution” (video of Jobs’s presentation; as an anthropologist, I’ll refrain from commenting on the evolutionary analogies):

We believe the PC, or more… importantly, the Mac can become the “digital hub” of our emerging digital lifestyle, with the ability to add tremendous value to … other digital devices.

… like camcorders, portable media players, cellphones, digital cameras, handheld organizers, etc. (Though they weren’t mentioned, other peripherals like printers and webcams also connect to PCs.)

The PC was thus going to serve as a hub, “not only adding value to these devices but interconnecting them, as well”.

At the time, key PC affordances which distinguished them from those other digital devices:

  • Big screen affording more complex user interfaces
  • Large, inexpensive hard disk storage
  • Burning DVDs and CDs
  • Internet connectivity, especially broadband
  • Running complex applications (including media processing software like the iLife suite)

Though Jobs pinpointed iLife applications as the basis for this “digital hub” vision, it sounds like FireWire was meant to be an even more important part of this vision. Of course, USB has supplanted FireWire in most use cases. It’s interesting, then, to notice that Apple only recently started shipping Macs with USB 3. In fact, DVD burning is absent from recent Macs. In 2001, the Mac might have been at the forefront of this “digital lifestyle” age. In 2013, the Mac has moved away from its role as “digital hub”.

In the meantime, the iPhone has become one of the best known examples of what I’m calling “wearable hubs”. It has a small screen and small, expensive storage (by today’s standards). It also can’t burn DVDs. But it does have nearly-ubiquitous Internet connectivity and can run fairly complex applications, some of which are adapted from the iLife suite. And though it does have wired connectivity (through Lightning or the “dock connector”), its main hub affordances have to do with Bluetooth.

It’s interesting to note that the same Steve Jobs, who used the “digital hub” concept to explain that the PC wasn’t dead in 2001, is partly responsible for popularizing the concept of “post-PC devices” six years later. One might perceive hypocrisy in this much delayed apparent flip-flop. On the other hand, Steve Jobs’s 2007 comments (video) were somewhat nuanced, as to the role of post-PC devices. What’s more interesting, though, is to think about the implications of the shift between two views of digital devices, regardless of Apple’s position through that shift.

Some post-PC devices (including the iPhone, until quite recently) do require a connection to a PC. In this sense, a smartphone might maintain its position with regards to the PC as digital hub. Yet, some of those devices are used independently of PCs, including by some people who never owned PCs.

Post-Smartphone Hubs

It’s possible to imagine a wearable hub outside of the smartphone (and tablet) paradigm. While smartphones are a convenient way to interconnect wearables, their hub-related affordances still sound limited: they lack large displays and their storage space is quite expensive. Their battery life may also be something to consider in terms of serving as hubs. Their form factors make some sense, when functioning as phones. Yet they have little to do with their use as hubs.

Part of the realization, for me, came from the fact that I’ve been using a tablet as something of an untethered hub. Since I use Bluetooth headphones, I can listen to podcasts and music while my tablet is in my backpack without being entangled in a cable. Sounds trivial but it’s one of these affordances I find quite significant. Delegating music playing functions to my tablet relates in part to battery life and use of storage. The tablet’s display has no importance in this scenario. In fact, given some communication between devices, my smartphone could serve as a display for my tablet. So could a “smartwatch” or “smartglasses”.

The Body Hub

Which led me to think about other devices which would work as wearable hubs. I originally thought about backpackable and pocketable devices.

But a friend had a more striking idea:

Under Armour’s Recharge Energy Suit may be an extreme version of this, one which would fit nicely among things Cathi Bond likes to discuss with Nora Young on The Sniffer. Nora herself has been discussing wearables on her blog as well as on her radio show. Sure, part of this concept is quite futuristic. But a sensor mesh undershirt is a neat idea for several reasons.

  • It’s easy to think of various sensors it may contain.
  • Given its surface area, it could hold enough battery power to supplement other devices.
  • It can be quite comfortable in cold weather and might even help diffuse heat in warmer climates.
  • Though wearable, it needs not be visible.
  • Thieves would probably have a hard time stealing it.
  • Vibration and haptic feedback on the body can open interesting possibilities.

Not that it’s the perfect digital hub and I’m sure there are multiple objections to a connected undershirt (including issues with radio signals). But I find the idea rather fun to think, partly because it’s so far away from the use of phones, glasses, and watches as smart devices.

Another thing I find neat, and it may partly be a coincidence, is the very notion of a “mesh”.

The Wearable Mesh

Mesh networking is a neat concept, which generates more hype than practical uses. As an alternative to WiFi access points and cellular connectivity, it’s unclear that it may “take the world by storm”. But as a way to connect personal devices, it might have some potential. After all, as Bernard Benhamou recently pointed out on France Culture’s Place de la toile, the Internet of Things may not require always-on full-bandwith connectivity. Typically, wearable sensors use fairly little bandwidth or only use it for limited amounts of time. A wearable mesh could connect wearable devices to one another while also exchanging data through the Internet itself.

Or with local devices. Smart cities, near field communication, and digital appliances occupy interesting positions among widely-discussed tendencies in the tech world. They may all have something to do with wearable devices. For instance, data exchanged between transit systems and their users could go through wearable devices. And while mobile payment systems can work through smartphones and other cellphones, wallet functions can also be fulfilled by other wearable devices.

Alternative Futures

Which might provide an appropriate segue into the ambivalence I feel toward the “wearable hub” concept I’m describing. Though I propose these ideas as if I were enthusiastic about them, they all give me pause. As a big fan of critical thinking, I like to think about “what might be” to generate questions and discussions exposing a diversity of viewpoints about the future.

Mass media discussions about these issues tend to focus on such things as privacy, availability, norms, and usefulness. Google Glass has generated quite a bit of buzz about all four. Other wearables may mainly raise issues for one or two of these broad dimensions. But the broad domain of wearable computing raises a lot more issues.

Technology enthusiasts enjoy discussing issues through the dualism between dystopia and utopia. An obvious issue with this dualism is that humans disagree about the two categories. Simply put, one person’s dystopia can be another person’s utopia, not to mention the nuanced views of people who see complex relationships between values and social change.

In such a context, a sociologist’s reflex may be to ask about the implications of these diverse values and opinions. For instance:

  • How do people construct these values?
  • Who decides which values are more important?
  • How might social groups cope with changes in values?

Discussing these issues and more, in a broad frame, might be quite useful. Some of the trickiest issues are raised after some changes in technology have already happened. From writing to cars, any technological context has unexpected implications. An ecological view of these implications could broaden the discussion.

I tend to like the concept of the “drift-off moment”, during which listeners (or readers) start thinking about the possibilities afforded a new tool (or concept). In the context of a sales pitch, the idea is that these possibilities are positive, a potential buyer is thinking about the ways she might use a newfangled device. But I also like the deeper process of thinking about all sorts of implications, regardless of their value.

So…

What might be the implications of a wearable hub?

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:

No Office Export in Keynote/Numbers for iPad?

To be honest, I’m getting even more excited about the iPad. Not that we get that much more info about it, but:

For one thing, the Pages for iPad webpage is explicitly stating Word support:

Attach them to an email as Pages files for Mac, Microsoft Word files, or PDF documents.

Maybe this is because Steve Jobs himself promised it to Walt Mossberg?
Thing is, the equivalent pages about Keynote for iPad and about Numbers for iPad aren’t so explicit:

The presentations you create in Keynote on your iPad can be exported as Keynote files for Mac or PDF documents

and…

To share your work, export your spreadsheet as a Numbers file for Mac or PDF document

Not a huge issue, but it seems strange that Apple would have such an “export to Microsoft Office” feature on only one of the three “iWork for iPad” apps. Now, the differences in the way exports are described may not mean that Keynote won’t be able to export to Microsoft PowerPoint or that Numbers won’t be able to export to Microsoft Excel. After all, these texts may have been written at different times. But it does sound like PowerPoint and Excel will be import-only, on the iPad.

Which, again, may not be that big an issue. Maybe iWork.com will work well enough for people’s needs. And some other cloud-based tools do support Keynote. (Though Google Docs and Zoho Show don’t.)

The reason I care is simple: I do share most of my presentation files. Either to students (as resources on Moodle) or to whole wide world (through Slideshare). My desktop outliner of choice, OmniOutliner, exports to Keynote and Microsoft Word. My ideal workflow would be to send, in parallel, presentation files to Keynote for display while on stage and to PowerPoint for sharing. The Word version could also be useful for sharing.

Speaking of presenting “slides” on stage, I’m also hoping that the “iPad Dock Connector to VGA Adapter” will support “presenter mode” at some point (though it doesn’t seem to be the case, right now). I also dream of a way to control an iPad presentation with some kind of remote. In fact, it’s not too hard to imagine it as an iPod touch app (maybe made by Appiction, down in ATX).

To be clear: my “presentation files” aren’t really about presenting so much as they are a way to package and organize items. Yes, I use bullet points. No, I don’t try to make the presentation sexy. My presentation files are acting like cue cards and like whiteboard snapshots. During a class, I use the “slides” as a way to keep track of where I planned the discussion to go. I can skip around, but it’s easier for me to get at least some students focused on what’s important (the actual depth of the discussion) because they know the structure (as “slides”) will be available online. Since I also podcast my lectures, it means that they can go back to all the material.

I also use “slides” to capture things we build in class, such as lists of themes from the readings or potential exam questions.  Again, the “whiteboard” idea. I don’t typically do the same thing during a one-time talk (say, at an unconference). But I still want to share my “slides,” at some point.

So, in all of these situations, I need a file format for “slides.” I really wish there were a format which could work directly out of the browser and could be converted back and forth with other formats (especially Keynote, OpenOffice, and PowerPoint). I don’t need anything fancy. I don’t even care about transitions, animations, or even inserting pictures. But, despite some friends’ attempts at making me use open solutions, I end up having to use presentation files.

Unfortunately, at this point, PowerPoint is the de facto standard for presentation files. So I need it, somehow. Not that I really need PowerPoint itself. But it’s still the only format I can use to share “slides.”

So, if Keynote for iPad doesn’t export directly to PowerPoint, it means that I’ll have to find another way to make my workflow fit.

Ah, well…

Why I Need an iPad

I’m one of those who feel the iPad is the right tool for the job.

This is mostly meant as a reply to this blogthread. But it’s also more generally about my personal reaction to Apple’s iPad announcement.

Some background.

I’m an ethnographer and a teacher. I read a fair deal, write a lot of notes, and work in a variety of contexts. These days, I tend to spend a good amount of time in cafés and other public places where I like to work without being too isolated. I also commute using public transit, listen to lots of podcast, and create my own. I’m also very aural.

I’ve used a number of PDAs, over the years, from a Newton MessagePad 130 (1997) to a variety of PalmOS devices (until 2008). In fact, some people readily associated me with PDA use.

As soon as I learnt about the iPod touch, I needed one. As soon as I’ve heard about the SafariPad, I wanted one. I’ve been an intense ‘touch user since the iPhone OS 2.0 release and I’m a happy camper.

(A major reason I never bought an iPhone, apart from price, is that it requires a contract.)

In my experience, the ‘touch is the most appropriate device for all sorts of activities which are either part of an other activity (reading during a commute) or are simply too short in duration to constitute an actual “computer session.” You don’t “sit down to work at your ‘touch” the way you might sit in front of a laptop or desktop screen. This works great for “looking up stufff” or “checking email.” It also makes a lot of sense during commutes in crowded buses or metros.

In those cases, the iPod touch is almost ideal. Ubiquitous access to Internet would be nice, but that’s not a deal-breaker. Alternative text-input methods would help in some cases, but I do end up being about as fast on my ‘touch as I was with Graffiti on PalmOS.

For other tasks, I have a Mac mini. Sure, it’s limited. But it does the job. In fact, I have no intention of switching for another desktop and I even have an eMachines collecting dust (it’s too noisy to make a good server).

What I miss, though, is a laptop. I used an iBook G3 for several years and loved it. For a little while later, I was able to share a MacBook with somebody else and it was a wonderful experience. I even got to play with the OLPC XO for a few weeks. That one was not so pleasant an experience but it did give me a taste for netbooks. And it made me think about other types of iPhone-like devices. Especially in educational contexts. (As I mentioned, I’m a teacher)

I’ve been laptop-less for a while, now. And though my ‘touch replaces it in many contexts, there are still times when I’d really need a laptop. And these have to do with what I might call “mobile sessions.”

For instance: liveblogging a conference or meeting. I’ve used my ‘touch for this very purpose on a good number of occasions. But it gets rather uncomfortable, after a while, and it’s not very fast. A laptop is better for this, with a keyboard and a larger form factor. But the iPad will be even better because of lower risks of RSI. A related example: just imagine TweetDeck on iPad.

Possibly my favourite example of a context in which the iPad will be ideal: presentations. Even before learning about the prospect of getting iWork on a tablet, presentations were a context in which I really missed a laptop.

Sure, in most cases, these days, there’s a computer (usually a desktop running XP) hooked to a projector. You just need to download your presentation file from Slideshare, show it from Prezi, or transfer it through USB. No biggie.

But it’s not the extra steps which change everything. It’s the uncertainty. Even if it’s often unfounded, I usually get worried that something might just not work, along the way. The slides might not show the same way as you see it because something is missing on that computer or that computer is simply using a different version of the presentation software. In fact, that software is typically Microsoft PowerPoint which, while convenient, fits much less in my workflow than does Apple Keynote.

The other big thing about presentations is the “presenter mode,” allowing you to get more content than (or different content from) what the audience sees. In most contexts where I’ve used someone else’s computer to do a presentation, the projector was mirroring the computer’s screen, not using it as a different space. PowerPoint has this convenient “presenter view” but very rarely did I see it as an available option on “the computer in the room.” I wish I could use my ‘touch to drive presentations, which I could do if I installed software on that “computer in the room.” But it’s not something that is likely to happen, in most cases.

A MacBook solves all of these problems. and it’s an obvious use for laptops. But how, then, is the iPad better? Basically because of interface. Switching slides on a laptop isn’t hard, but it’s more awkward than we realize. Even before watching the demo of Keynote on the iPad, I could simply imagine the actual pleasure of flipping through slides using a touch interface. The fit is “natural.”

I sincerely think that Keynote on the iPad will change a number of things, for me. Including the way I teach.

Then, there’s reading.

Now, I’m not one of those people who just can’t read on a computer screen. In fact, I even grade assignments directly from the screen. But I must admit that online reading hasn’t been ideal, for me. I’ve read full books as PDF files or dedicated formats on PalmOS, but it wasn’t so much fun, in terms of the reading process. And I’ve used my ‘touch to read things through Stanza or ReadItLater. But it doesn’t work so well for longer reading sessions. Even in terms of holding the ‘touch, it’s not so obvious. And, what’s funny, even a laptop isn’t that ideal, for me, as a reading device. In a sense, this is when the keyboard “gets in the way.”

Sure, I could get a Kindle. I’m not a big fan of dedicated devices and, at least on paper, I find the Kindle a bit limited for my needs. Especially in terms of sources. I’d like to be able to use documents in a variety of formats and put them in a reading list, for extended reading sessions. No, not “curled up in bed.” But maybe lying down in a sofa without external lighting. Given my experience with the ‘touch, the iPad is very likely the ideal device for this.

Then, there’s the overall “multi-touch device” thing. People have already been quite creative with the small touchscreen on iPhones and ‘touches, I can just imagine what may be done with a larger screen. Lots has been said about differences in “screen real estate” in laptop or desktop screens. We all know it can make a big difference in terms of what you can display at the same time. In some cases, two screens isn’t even a luxury, for instance when you code and display a page at the same time (LaTeX, CSS…). Certainly, the same qualitative difference applies to multitouch devices. Probably even more so, since the display is also used for input. What Han found missing in the iPhone’s multitouch was the ability to use both hands. With the iPad, Han’s vision is finding its space.

Oh, sure, the iPad is very restricted. For instance, it’s easy to imagine how much more useful it’d be if it did support multitasking with third-party apps. And a front-facing camera is something I was expecting in the first iPhone. It would just make so much sense that a friend seems very disappointed by this lack of videoconferencing potential. But we’re probably talking about predetermined expectations, here. We’re comparing the iPad with something we had in mind.

Then, there’s the issue of the competition. Tablets have been released and some multitouch tablets have recently been announced. What makes the iPad better than these? Well, we could all get in the same OS wars as have been happening with laptops and desktops. In my case, the investment in applications, files, and expertise that I have made in a Mac ecosystem rendered my XP years relatively uncomfortable and me appreciate returning to the Mac. My iPod touch fits right in that context. Oh, sure, I could use it with a Windows machine, which is in fact what I did for the first several months. But the relationship between the iPhone OS and Mac OS X is such that using devices in those two systems is much more efficient, in terms of my own workflow, than I could get while using XP and iPhone OS. There are some technical dimensions to this, such as the integration between iCal and the iPhone OS Calendar, or even the filesystem. But I’m actually thinking more about the cognitive dimensions of recognizing some of the same interface elements. “Look and feel” isn’t just about shiny and “purty.” It’s about interactions between a human brain, a complex sensorimotor apparatus, and a machine. Things go more quickly when you don’t have to think too much about where some tools are, as you’re working.

So my reasons for wanting an iPad aren’t about being dazzled by a revolutionary device. They are about the right tool for the job.

Homeroasting and Coffee Geekness

I’m a coffee geek. By which I mean that I have a geeky attitude to coffee. I’m passionate about the crafts and arts of coffee making, I seek coffee-related knowledge wherever I can find it, I can talk about coffee until people’s eyes glaze over (which happens more quickly than I’d guess possible), and I even dream about coffee gadgets. I’m not a typical gadget freak, as far as geek culture goes, but coffee is one area where I may invest in some gadgetry.

Perhaps my most visible acts of coffee geekery came in the form of updates I posted through diverse platforms about my home coffee brewing experiences. Did it from February to July. These posts contained cryptic details about diverse measurements, including water temperature and index of refraction. It probably contributed to people’s awareness of my coffee geek identity, which itself has been the source of fun things like a friend bringing me back coffee from Ethiopia.

But I digress, a bit. This is both about coffee geekness in general and about homeroasting in particular.

See, I bought myself this Hearthware i-Roast 2 dedicated homeroasting device. And I’m dreaming about coffee again.

Been homeroasting since December 2002, at the time I moved to Moncton, New Brunswick and was lucky enough to get in touch with Terry Montague of Down Esst Coffee.

Though I had been wishing to homeroast for a while before that and had become an intense coffee-lover fifteen years prior to contacting him, Terry is the one who enabled me to start roasting green coffee beans at home. He procured me a popcorn popper, sourced me some quality green beans, gave me some advice. And off I was.

Homeroasting is remarkably easy. And it makes a huge difference in one’s appreciation of coffee. People in the coffee industry, especially baristas and professional roasters, tend to talk about the “channel” going from the farmer to the “consumer.” In some ways, homeroasting gets the coffee-lover a few steps closer to the farmer, both by eliminating a few intermediaries in the channel and by making coffee into much less of a commodity. Once you’ve spent some time smelling the fumes emanated by different coffee varietals and looking carefully at individual beans, you can’t help but get a deeper appreciation for the farmer’s and even the picker’s work. When you roast 150g or less at a time, every coffee bean seems much more valuable. Further, as you experiment with different beans and roast profiles, you get to experience coffee in all of its splendour.

A popcorn popper may sound like a crude way to roast coffee. And it might be. Naysayers may be right in their appraisal of poppers as a coffee roasting method. You’re restricted in different ways and it seems impossible to produce exquisite coffee. But having roasted with a popper for seven years, I can say that my poppers gave me some of my most memorable coffee experiences. Including some of the most pleasant ones, like this organic Sumatra from Theta Ridge Coffee that I roasted in my campus appartment at IUSB and brewed using my beloved Brikka.

Over the years, I’ve roasted a large variety of coffee beans. I typically buy a pound each of three or four varietals and experiment with them for a while.

Mostly because I’ve been moving around quite a bit, I’ve been buying green coffee beans from a rather large variety of places. I try to buy them locally, as much as possible (those beans have travelled far enough and I’ve had enough problems with courier companies). But I did participate in a few mail orders or got beans shipped to me for some reason or another. Sourcing green coffee beans has almost been part of my routine in those different places where I’ve been living since 2002: Moncton, Montreal, Fredericton, South Bend, Northampton, Brockton, Cambridge, and Austin. Off the top of my head, I’ve sourced beans from:

  1. Down East
  2. Toi, moi & café
  3. Brûlerie Saint-Denis
  4. Brûlerie des quatre vents
  5. Terra
  6. Theta Ridge
  7. Dean’s Beans
  8. Green Beanery
  9. Cuvée
  10. Fair Bean
  11. Sweet Maria’s
  12. Evergreen Coffee
  13. Mon café vert
  14. Café-Vrac
  15. Roastmasters
  16. Santropol

And probably a few other places, including this one place in Ethiopia where my friend Erin bought some.

So, over the years, I got beans from a rather large array of places and from a wide range of regional varietals.

I rapidly started blending freshly-roasted beans. Typically, I would start a blend by roasting three batches in a row. I would taste some as “single origin” (coffee made from a single bean varietal, usually from the same farm or estate), shortly after roasting. But, typically, I would mix my batches of freshly roasted coffee to produce a main blend. I would then add fresh batches after a few days to fine-tune the blend to satisfy my needs and enhance my “palate” (my ability to pick up different flavours and aromas).

Once the quantity of green beans in a particular bag would fall below an amount I can reasonably roast as a full batch (minimum around 100g), I would put those green beans in a pre-roast blend, typically in a specially-marked ziplock bag. Roasting this blend would usually be a way for me to add some complexity to my roasted blends.

And complexity I got. Lots of diverse flavours and aromas. Different things to “write home about.”

But I was obviously limited in what I could do with my poppers. The only real controls that I had in homeroasting, apart from blending, consisted in the bean quantity and roasting time. Ambient temperature was clearly a factor, but not one over which I was able to exercise much control. Especially since I frequently ended up roasting outside, so as to not incommodate people with fumes, noise, and chaff. The few homeroast batches which didn’t work probably failed because of low ambient temperature.

One reason I stuck with poppers for so long was that I had heard that dedicated roasters weren’t that durable. I’ve probably used three or four different hot air popcorn poppers, over the years. Eventually, they just stop working, when you use them for coffee beans. As I’d buy them at garage sales and Salvation Army stores for 3-4$, replacing them didn’t feel like such a financially difficult thing to do, though finding them could occasionally be a challenge. Money was also an issue. Though homeroasting was important for me, I wasn’t ready to pay around 200$ for an entry-level dedicated roaster. I was thinking about saving money for a Behmor 1600, which offers several advantages over other roasters. But I finally gave in and bought my i-Roast as a kind of holiday gift to myself.

One broad reason is that my financial situation has improved since I started a kind of partial professional reorientation (PPR). I have a blogpost in mind about this PPR, and I’ll probably write it soon. But this post isn’t about my PPR.

Although, the series of events which led to my purchase does relate to my PPR, somehow.

See, the beans I (indirectly) got from Roastmasters came from a friend who bought a Behmor to roast cocoa beans. The green coffee beans came with the roaster but my friend didn’t want to roast coffee in his brand new Behmor, to avoid the risk of coffee oils and flavours getting into his chocolate. My friend asked me to roast some of these beans for his housemates (he’s not that intensely into coffee, himself). When I went to drop some homeroasted coffee by the Station C co-working space where he spends some of his time, my friend was discussing a project with Duncan Moore, whom I had met a few times but with whom I had had few interactions. The three of us had what we considered a very fruitful yet very short conversation. Later on, I got to do a small but fun project with Duncan. And I decided to invest that money into coffee.

A homeroaster seemed like the most appropriate investment. The Behmor was still out of reach but the i-Roast seemed like a reasonable purchase. Especially if I could buy it used.

But I was also thinking about buying it new, as long as I could get it quickly. It took me several years to make a decision about this purchase but, once I made it, I wanted something as close to “instant gratification” as possible. In some ways, the i-Roast was my equivalent to Little Mrs Sommers‘s “pair of silk stockings.”

At the time, Mon café vert seemed like the only place where I could buy a new i-Roast. I tried several times to reach them to no avail. As I was in the Mile-End as I decided to make that purchase, I went to Caffè in Gamba, both to use the WiFi signal and to check if, by any chance, they might not have started selling roasters. They didn’t, of course, homeroasters isn’t mainstream enough. But, as I was there, I saw the Hario Ceramic Coffee Mill Skerton, a “hand-cranked” coffee grinder about which I had read some rather positive reviews.

For the past few years, I had been using a Bodum Antigua conical burr electric coffee grinder. This grinder was doing the job, but maybe because of “wear and tear,” it started taking a lot longer to grind a small amount of coffee. The grind took so long, at some points, that the grounds were warm to the touch and it seemed like the grinder’s motor was itself heating.

So I started dreaming about the Baratza Vario, a kind of prosumer electric grinder which seemed like the ideal machine for someone who uses diverse coffee making methods. The Vario is rather expensive and seemed like overkill, for my current coffee setup. But I was lusting over it and, yes, dreaming about it.

One day, maybe, I’ll be able to afford a Vario.

In the meantime, and more reasonably, I had been thinking about “Turkish-style mills.” A friend lent me a box-type manual mill at some point and I did find it produced a nice grind, but it wasn’t that convenient for me, partly because the coffee drops into a small drawer which rapidly gets full. A handmill seemed somehow more convenient and there are some generic models which are sold in different parts of the World, especially in the Arab World. So I got the impression that I might be able to find handmills locally and started looking for them all over the place, enquiring at diverse stores and asking friends who have used those mills in the past. Of course, they can be purchased online. But they end up being relatively expensive and my manual experience wasn’t so positive as to convince me to spend so much money on one.

The Skerton was another story. It was much more convenient than a box-type manual mill. And, at Gamba, it was inexpensive enough for me to purchase it on the spot. I don’t tend to do this very often so I did feel strange about such an impulse purchase. But I certainly don’t regret it.

Especially since it complements my other purchases.

So, going to the i-Roast.

Over the years, I had been looking for the i-Roast and Behmor at most of the obvious sites where one might buy used devices like these. eBay, Craig’s List, Kijiji… As a matter of fact, I had seen an i-Roast on one of these, but I was still hesitating. Not exactly sure why, but it probably had to do with the fact that these homeroasters aren’t necessarily that durable and I couldn’t see how old this particular i-Roast was.

I eventually called to find out, after taking my decision to get an i-Roast. Turns out that it’s still under warranty, is in great condition, and was being sold by a very interesting (and clearly trustworthy) alto singer who happens to sing with a friend of mine who is also a local beer homebrewer. The same day I bought the roaster, I went to the cocoa-roasting friend’s place and saw a Behmor for the first time. And I tasted some really nice homemade chocolate. And met other interesting people including a couple that I saw, again, while taking the bus after purchasing the roaster.

The series of coincidences in that whole situation impressed me in a sense of awe. Not out of some strange superstition or other folk belief. But different things are all neatly packaged in a way that most of my life isn’t. Nothing weird about this. The packaging is easy to explain and mostly comes from my own perception. The effect is still there that it all fits.

And the i-Roast 2 itself fits, too.

It’s clearly not the ultimate coffee geek’s ideal roaster. But I get the impression it could become so. In fact, one reason I hesitated to buy the i-Roast 2 is that I was wondering if Hearthware might be coming out with the i-Roast 3, in the not-so-distant future.

I’m guessing that Hearthware might be getting ready to release a new roaster. I’m using unreliable information, but it’s still an educated guess. So, apparently…

I could just imagine what the i-Roast 3 might be. As I’m likely to get, I have a number of crazy ideas.

One “killer feature” actually relates both to the differences between the i-Roast and i-Roast 2 as well as to the geek factor behind homeroasting: roast profiles as computer files. Yes, I know, it sounds crazy. And, somehow, it’s quite unlikely that Hearthware would add such a feature on an entry-level machine. But I seriously think it’d make the roaster much closer to a roasting geek’s ultimate machine.

For one thing, programming a roast profile on the i-Roast is notoriously awkward. Sure, you get used to it. But it’s clearly suboptimal. And one major improvement of the i-Roast 2 over the original i-Roast is that the original version didn’t maintain profiles if you unplugged it. The next step, in my mind, would be to have some way to transfer a profile from a computer to the roaster, say via a slot for SD cards or even a USB port.

What this would open isn’t only the convenience of saving profiles, but actually a way to share them with fellow homeroasters. Since a lot in geek culture has to do with sharing information, a neat effect could come out of shareable roast profiles. In fact, when I looked for example roast profiles, I found forum threads, guides, and incredibly elaborate experiments. Eventually, it might be possible to exchange roasting profiles relating to coffee beans from the same shipment and compare roasting. Given the well-known effects of getting a group of people using online tools to share information, this could greatly improve the state of homeroasting and even make it break out of the very small niche in which it currently sits.

Of course, there are many problems with that approach, including things as trivial as voltage differences as well as bigger issues such as noise levels:

[youtube=http://www.youtube.com/watch?v=c88nEXYCbfs]

But I’m still dreaming about such things.

In fact, I go a few steps further. A roaster which could somehow connect to a computer might also be used to track data about temperature and voltage. In my own experiments with the i-Roast 2, I’ve been logging temperatures at 15 second intervals along with information about roast profile, quantity of beans, etc. It may sound extreme but it already helped me achieve a result I wanted to achieve. And it’d be precisely the kind of information I would like to share with other homeroasters, eventually building a community of practice.

Nothing but geekness, of course. Shall the geek inherit the Earth?

Personal Devices

Still thinking about touch devices, such as the iPod touch and the rumoured “Apple Tablet.”

Thinking out loud. Rambling even more crazily than usual.

Something important about those devices is the need for a real “Personal Digital Assistant.” I put PDAs as a keyword for my previous post because I do use the iPod touch like I was using my PalmOS and even NewtonOS devices. But there’s more to it than that, especially if you think about cloud computing and speech technologies.
I mentioned speech recognition in that previous post. SR tends to be a pipedream of the computing world. Despite all the hopes put into realtime dictation, it still hasn’t taken off in a big way. One reason might be that it’s still somewhat cumbersome to use, in current incarnations. Another reason is that it’s relatively expensive as a standalone product which requires some getting used to. But I get the impression that another set of reasons has to do with the fact that it’s mostly fitting on a personal device. Partly because it needs to be trained. But also because voice itself is a personal thing.

Cloud computing also takes a new meaning with a truly personal device. It’s no surprise that there are so many offerings with some sort of cloud computing feature in the App Store. Not only do Apple’s touch devices have limited file storage space but the notion of accessing your files in the cloud go well with a personal device.
So, what’s the optimal personal device? I’d say that Apple’s touch devices are getting close to it but that there’s room for improvement.

Some perspective…

Originally, the PC was supposed to be a “personal” computer. But the distinction was mostly with mainframes. PCs may be owned by a given person, but they’re not so tied to that person, especially given the fact that they’re often used in a single context (office or home, say). A given desktop PC can be important in someone’s life, but it’s not always present like a personal device should be. What’s funny is that “personal computers” became somewhat more “personal” with the ‘Net and networking in general. Each computer had a name, etc. But those machines remained somewhat impersonal. In many cases, even when there are multiple profiles on the same machine, it’s not so safe to assume who the current user of the machine is at any given point.

On paper, the laptop could have been that “personal device” I’m thinking about. People may share a desktop computer but they usually don’t share their laptop, unless it’s mostly used like a desktop computer. The laptop being relatively easy to carry, it’s common for people to bring one back and forth between different sites: work, home, café, school… Sounds tautological, as this is what laptops are supposed to be. But the point I’m thinking about is that these are still distinct sites where some sort of desk or table is usually available. People may use laptops on their actual laps, but the form factor is still closer to a portable desktop computer than to the kind of personal device I have in mind.

Then, we can go all the way to “wearable computing.” There’s been some hype about wearable computers but it has yet to really be part of our daily lives. Partly for technical reasons but partly because it may not really be what people need.

The original PDAs (especially those on NewtonOS and PalmOS) were getting closer to what people might need, as personal devices. The term “personal digital assistant” seemed to encapsulate what was needed. But, for several reasons, PDAs have been having a hard time. Maybe there wasn’t a killer app for PDAs, outside of “vertical markets.” Maybe the stylus was the problem. Maybe the screen size and bulk of the device weren’t getting to the exact points where people needed them. I was still using a PalmOS device in mid-2008 and it felt like I was among the last PDA users.
One point was that PDAs had been replaced by “smartphones.” After a certain point, most devices running PalmOS were actually phones. RIM’s Blackberry succeeded in a certain niche (let’s use the vague term “professionals”) and is even beginning to expand out of it. And devices using other OSes have had their importance. It may not have been the revolution some readers of Pen Computing might have expected, but the smartphone has been a more successful “personal device” than the original PDAs.

It’s easy to broaden our focus from smartphones and think about cellphones in general. If the 3.3B figure can be trusted, cellphones may already be outnumbering desktop and laptop computers by 3:1. And cellphones really are personal. You bring them everywhere; you don’t need any kind of surface to use them; phone communication actually does seem to be a killer app, even after all this time; there are cellphones in just about any price range; cellphone carriers outside of Canada and the US are offering plans which are relatively reasonable; despite some variation, cellphones are rather similar from one manufacturer to the next… In short, cellphones already were personal devices, even before the smartphone category really emerged.

What did smartphones add? Basically, a few PDA/PIM features and some form of Internet access or, at least, some form of email. “Whoa! Impressive!”

Actually, some PIM features were already available on most cellphones and Internet access from a smartphone is in continuity with SMS and data on regular cellphones.

What did Apple’s touch devices add which was so compelling? Maybe not so much, apart from the multitouch interface, a few games, and integration with desktop/laptop computers. Even then, most of these changes were an evolution over the basic smartphone concept. Still, it seems to have worked as a way to open up personal devices to some new dimensions. People now use the iPhone (or some other multitouch smartphone which came out after the iPhone) as a single device to do all sorts of things. Around the World, multitouch smartphones are still much further from being ubiquitous than are cellphones in general. But we could say that these devices have brought the personal device idea to a new phase. At least, one can say that they’re much more exciting than the other personal computing devices.

But what’s next for personal devices?

Any set of buzzphrases. Cloud computing, speech recognition, social media…

These things can all come together, now. The “cloud” is mostly ready and personal devices make cloud computing more interesting because they’re “always-on,” are almost-wearable, have batteries lasting just about long enough, already serve to keep some important personal data, and are usually single-user.

Speech recognition could go well with those voice-enabled personal devices. For one thing, they already have sound input. And, by this time, people are used to seeing others “talk to themselves” as cellphones are so common. Plus, voice recognition is already understood as a kind of security feature. And, despite their popularity, these devices could use a further killer app, especially in terms of text entry and processing. Some of these devices already have voice control and it’s not so much of a stretch to imagine them having what’s needed for continuous speech recognition.

In terms of getting things onto the device, I’m also thinking about such editing features as a universal rich-text editor (à la TinyMCE), predictive text, macros, better access to calendar/contact data, ubiquitous Web history, multiple pasteboards, data detectors, Automator-like processing, etc. All sorts of things which should come from OS-level features.

“Social media” may seem like too broad a category. In many ways, those devices already take part in social networking, user-generated content, and microblogging, to name a few areas of social media. But what about a unified personal profile based on the device instead of the usual authentication method? Yes, all sorts of security issues. But aren’t people unconcerned about security in the case of social media? Twitter accounts are being hacked left and right yet Twitter doesn’t seem to suffer much. And there could be added security features on a personal device which is meant to really integrate social media. Some current personal devices already work well as a way to keep login credentials to multiple sites. The next step, there, would be to integrate all those social media services into the device itself. We maybe waiting for OpenSocial, OpenID, OAuth, Facebook Connect, Google Connect, and all sorts of APIs to bring us to an easier “social media workflow.” But a personal device could simplify the “social media workflow” even further, with just a few OS-based tweaks.

Unlike my previous, I’m not holding my breath for some specific event which will bring us the ultimate personal device. After all, this is just a new version of my ultimate handheld device blogpost. But, this time, I was focusing on what it means for a device to be “personal.” It’s even more of a drafty draft than my blogposts usually have been ever since I decided to really RERO.

So be it.

Speculating on Apple's Touch Strategy

This is mere speculation on my part, based on some rumours.

I’m quite sure that Apple will come up with a video-enabled iPod touch on September 9, along with iTunes 9 (which should have a few new “social networking” features). This part is pretty clear from most rumour sites.

AppleInsider | Sources: Apple to unveil new iPod lineup on September 9.

Progressively, Apple will be adopting a new approach to marketing its touch devices. Away from the “poorperson’s iPhone” and into the “tiny but capable computer” domain. Because the 9/9 event is supposed to be about music, one might guess that there will be a cool new feature or two relating to music. Maybe lyrics display, karaoke mode, or whatever else. Something which will simultaneously be added to the iPhone but would remind people that the iPod touch is part of the iPod family. Apple has already been marketing the iPod touch as a gaming platform, so it’s not a radical shift. But I’d say the strategy is to make Apple’s touch devices increasingly more attractive, without cannibalizing sales in the MacBook family.

Now, I really don’t expect Apple to even announce the so-called “Tablet Mac” in September. I’m not even that convinced that the other devices Apple is preparing for expansion of its touch devices lineup will be that close to the “tablet” idea. But it seems rather clear, to me, that Apple should eventually come up with other devices in this category. Many rumours point to the same basic notion, that Apple is getting something together which will have a bigger touchscreen than the iPhone or iPod touch. But it’s hard to tell how this device will fit, in the grand scheme of things.

It’s rather obvious that it won’t be a rebirth of the eMate the same way that the iPod touch wasn’t a rebirth of the MessagePad. But it would make some sense for Apple to target some educational/learning markets, again, with an easy-to-use device. And I’m not just saying this because the rumoured “Tablet Mac” makes me think about the XOXO. Besides, the iPod touch is already being marketed to educational markets through the yearly “Back to school” program which (surprise!) ends on the day before the September press conference.

I’ve been using an iPod touch (1st Generation) for more than a year, now, and I’ve been loving almost every minute of it. Most of the time, I don’t feel the need for a laptop, though I occasionally wish I could buy a cheap one, just for some longer writing sessions in cafés. In fact, a friend recently posted information about some Dell Latitude D600 laptops going for a very low price. That’d be enough for me at this point. Really, my iPod touch suffices for a lot of things.

Sadly, my iPod touch seems to have died, recently, after catching some moisture. If I can’t revive it and if the 2nd Generation iPod touch I bought through Kijiji never materializes, I might end up buying a 3rd Generation iPod touch on September 9, right before I start teaching again. If I can get my hands on a working iPod touch at a good price before that, I may save the money in preparation for an early 2010 release of a new touch device from Apple.

Not that I’m not looking at alternatives. But I’d rather use a device which shares enough with the iPod touch that I could migrate easily, synchronize with iTunes, and keep what I got from the App Store.

There’s a number of things I’d like to get from a new touch device. First among them is a better text entry/input method. Some of the others could be third-party apps and services. For instance, a full-featured sharing app. Or true podcast synchronization with media annotation support (à la Revver or Soundcloud). Or an elaborate, fully-integrated logbook with timestamps, Twitter support, and outlining. Or even a high-quality reference/bibliography manager (think RefWorks/Zotero/Endnote). But getting text into such a device without a hardware keyboard is the main challenge. I keep thinking about all sorts of methods, including MessagEase and Dasher as well as continuous speech recognition (dictation). Apple’s surely thinking about those issues. After all, they have some handwriting recognition systems that they aren’t really putting to any significant use.

Something else which would be quite useful is support for videoconferencing. Before the iPhone came out, I thought Apple may be coming out with iChat Mobile. Though a friend announced the iPhone to me by making reference to this, the position of the camera at the back of the device and the fact that the original iPhone’s camera only supported still pictures (with the official firmware) made this dream die out, for me. But a “Tablet Mac” with an iSight-like camera and some form of iChat would make a lot of sense, as a communication device. Especially since iChat already supports such things as screen-sharing and slides. Besides, if Apple does indeed move in the direction of some social networking features, a touch device with an expanded Address Book could take a whole new dimension through just a few small tweaks.

This last part I’m not so optimistic about. Apple may know that social networking is important, at this point in the game, but it seems to approach it with about the same heart as it approached online services with eWorld, .Mac, and MobileMe. Of course, they have the tools needed to make online services work in a “social networking” context. But it’s possible that their vision is clouded by their corporate culture and some remnants of the NIH problem.

Ah, well…

Sharing Tool Wishlist

The following is an edited version of a wishlist I had been keeping on the side. The main idea is to define what would be, in my mind, the “ultimate social bookmarking system.” Which, obviously, goes way beyond social bookmarking. In a way, I even conceive of it as the ultimate tool for sharing online content. Yes, it’s that ambitious. Will it ever exist? Probably not. Should it exist? I personally think so. But I may be alone in this. Surely, you’ll tell me that I am indeed alone, which is fine. As long as you share your own wishlist items.

The trigger for my posting this is that someone contacted me, asking for what I’d like in a social bookmarking system. I find this person’s move quite remarkable, as a thoughtful strategy. Not only because this person contacted me directly (almost flattering), but because such a request reveals an approach to listening and responding to people’s needs that I find lacking in some software development circles.

This person’s message served as a prompt for my blogging this, but I’ve been meaning to blog this for a while. In fact, my guess is that I created a first version of this wishlist in 2007 after having it on my mind for a while before that. As such, it represents a type of “diachronic” or “longitudinal” view of social bookmarking and the way it works in the broader scheme of social media.

Which also means that I wrote this before I heard about Google Wave. In fact, I’m still unclear about Google Wave and I’ll need to blog about that. Not that I expect Wave to fulfill all the needs I set up for a sharing tool, but I get the impression that Google is finally putting some cards on the table.

The main part of this post is in outline form. I often think through outlines, especially with such a type of notes. I fully realize that it may not be that clear, as a structure, for other people to understand. Some of these bullet points cover a much broader issue than what they look like. But the overall idea might be fairly obvious to grasp, even if it may sound crazy to other people.

I’m posting this to the benefit of anyone who may wish to build the killer app for social media. Of course, it’s just one man’s opinion. But it’s my entitled opinion.

Concepts

What do we share online?

  • “Link”
  • “Page”
  • Identified content
  • Text
    • Narrative
    • Contact information
    • Event description
  • Contact information
  • Event invitation
  • Image
  • Recording
  • Structured content
  • Snippet
  • Access to semi-private content
  • Site’s entry point

Selective sharing

Private
  • Archiving
  • Cloud access
Individually shared
  • “Check this out”
  • Access to address book
  • Password protection
  • Specialization/expertise
  • Friendship
Group shared
  • Shared interests (SIG)
  • Collaboration (task-based)
Shared through network
  • Define identity in network
  • Semi-public
Public
  • Publishing
  • Processed
  • Reading lists

Notetaking

  • Active reading
  • Anchoring text
  • Ad hoc list of bookmarks
  • “Empty URL”
    • Create container/page
    • Personal notes

Todos

  • To read
  • To blog
  • To share
  • To update
  • Projects
    • GTD
    • Contexts
  • Add to calendar (recognized as event)

Outlining/Mindmapping

  • Manage lists of links
  • Prioritize
  • Easily group

Social aspects of sharing

  • Gift economy
  • Personal interaction
  • Trust
  • Hype
  • Value
  • Customized

Cloud computing

  • Webware
  • “Online disk”
  • Without download
  • Touch devices
  • Edit online

Personal streaming

  • Activities through pages
  • Logging
  • Flesh out personal profile

Tagging

  • “Folksonomy”
  • Enables non-hierarchical structure
  • Semantic fields
  • Related tags
  • Can include hierarchy
  • Tagclouds define concept map

Required Features

Crossplatform, crossbrowser

  • Browser-specific tools
  • Bookmarklets
  • Complete access through cloud
Keyboard shortcuts
  • Quick add (to account)
  • Vote
  • Bookmark all tabs (à la Flock)
  • Quick tags

Related pages

Recommended
  • Based on social graph
  • Based on tags
  • Based on content
  • Based on popularity
  • Pointing to this page

Quickly enter links

  • Add in place (while editing)
  • Similar to “spell as you type”
  • Incremental search
  • Add full link (title, URL, text, metadata)

Archiving

  • Prevent linkrot
  • Prepare for post-processing (offline reading, blogging…)
  • Enable bulk processing
  • Maintain version history
  • Internet Archive

Automatic processing

  • Tags
  • Summary
  • Wordcount
  • Reading time
  • Language(s)
  • Page structure analysis
  • Geotagging
  • Vote

Thread following

  • Blog comments
  • Forum comments
  • Trackbacks
  • Pings

Exporting

All
  • Archiving
  • Prepare for import
  • Maintain hierarchy
Selected
  • Tag
  • Category
  • Recently used
  • Shared
  • Site homepage
  • Blogroll
  • Blogs
Formats
  • Other services
  • HTML
  • RSS
  • OPML
  • Widget
Features
  • Comments
  • Tags
  • Statistics
  • Content

Offline processing

  • Browser-based
  • Device based
  • Offline archiving
  • Include content
  • Synchronization

Microblogging support

  • Laconi.ca/Identi.ca
  • Twitter
  • Ping.fm
  • Jaiku

Fixed/Static URL

  • Prevent linkrot
  • Maintain list for same page
  • Short URLs
  • Automatically generated
  • Expansion on mouseover
  • Statistics

Authentication

  • Use of resources
  • Identify
  • Privacy
  • Unnecessary for basic processing
  • Sticks (no need to login frequently)
  • Access to contacts and social graph
  • Multiple accounts
    • Personal/professional
    • Contexts
    • Group accounts
  • Premium accounts
    • Server space
    • Usage statistics
    • Promotion
  • Support
    • OpenID
      • As group login
    • Google Accounts
    • Facebook Connect
    • OAuth

Integration

  • Web history
  • Notebook
  • Blogging platform
  • Blog editor
  • Microblogging platform
  • Logbook
  • General purpose content editor
  • Toolbar
  • URL shortening
  • Address book
  • Social graph
  • Personal profile
  • Browser
    • Bookmarks
    • History
    • Autocomplete
  • Analytics
  • Email
  • Search
    • Online
    • Offline

Related Tools

  • Diigo
  • WebCitation
  • Ping.fm
  • BackType
  • Facebook share
  • Blog This
  • Link This
  • Share this
  • Digg
  • Plum
  • Spurl
  • CoComments
  • MyBlogLog
  • TwtVite
  • Twistory
  • Windows Live Writer
  • Magnolia
  • Stumble Upon
  • Delicious
  • Google Reader
  • Yahoo Pipes
  • Google Notebook
  • Zoho Notebook
  • Google Browser Sync
  • YouTube
  • Flock
  • Zotero

Relevant Blogposts