One thing I like about this text is its tone. There’s an honesty, an ingenuity that I find rare in this type of writing.
- startup ideas
- The background is important, in terms of the type of ideas about which we’re constructing something.
- what do you wish someone would make for you?
- My own itch has to do with Diigo, actually. There’s a lot I wish Diigo would make for me. I may be perceived as an annoyance, but I think my wishlist may lead to something bigger and possibly quite successful.
- The difference between this question and the “scratch your own itch” principle seems significant, and this distinction may have some implications in terms of success: we’re already talking about others, not just running ideas in our own head.
- what do you wish someone would make for you?
- It’s somewhat different from the well-known “scratch your own itch” principle. In this difference might be located something significant. In a way, part of the potential for this version to lead to success comes from the fact that it’s already connected with others, instead of being about running ideas in your own mind.
- grow organically
- The core topic of the piece, put in a comparative context. The comparison isn’t the one people tend to make and one may argue about the examples used. But the concept of organic ideas is fascinating and inspiring.
- you decide, from afar,
- What we call, in anthropology, the “armchair” approach. Also known as “backbenching.” For this to work, you need to have a deep knowledge of the situation, which is part of the point in this piece. Nice that it’s not demonizing this position but putting it in context.
was the first type
- One might argue that it was a hybrid case. Although, it does sound like the very beginnings of Apple weren’t about “thinking from afar.”
- class of users other than you
- Since developers are part of a very specific “class” of people, this isn’t insignificant a way to phrase this.
- They still rely on this principle today, incidentally.
The iPhone is the phone Steve Jobs wants.
- Apple tends to be perceived in a different light. According to many people, it’s the “textbook example” of a company where decisions are made without concerns for what people need. “Steve Jobs uses a top-down approach,” “They don’t even use focus groups,” “They don’t let me use their tools the way I want to use them.” But we’re not talking about the same distinction between top-down and bottom-up. Though “organic ideas” seem to imply that it’s a grassroots/bottom-up phenomenon, the core distinction isn’t about the origin of the ideas (from the “top,” in both cases) but on the reasoning behind these ideas.
- We didn’t need this software ourselves.
- Sounds partly like a disclaimer but this approach is quite common and “there’s nothing wrong with it.”
- comparatively old
- Age and life experience make for an interesting angle. It’s not that this strategy needs people of a specific age to work. It’s that there’s a connection between one’s experience and the way things may pan out.
- There is no sharp line between the two types of ideas,
- Those in the “engineering worldview” might go nuts, at this point. I can hear the claims of “hand waving.” But we’re talking about something complex, here, not a merely complicated problem.
- Apple type
- One thing to note in the three examples here: they’re all made by pairs of guys. Jobs and Woz, Gates and Allen, Page and Brin. In many cases, the formula might be that one guy (or gal, one wishes) comes up with ideas knowing that the other can implement them. Again, it’s about getting somebody else to build it for you, not about scratching your own itch.
- Bill Gates was writing something he would use
- Again, Gates may not be the most obvious example, since he’s mostly known for another approach. It’s not inaccurate to say he was solving his own problem, at the time, but it may not be that convincing as an example.
- Larry and Sergey when they wrote the first versions of Google.
- Although, the inception of the original ideas was academic in context. They weren’t solving a search problem or thinking about monetization. They were discovering the power of CitationRank.
- generally preferable
- Nicely relativistic.
- It takes experience
to predict what other people will want.
- And possibly a lot more. Interesting that he doesn’t mention empirical data.
- young founders
- They sound like a fascinating group to observe. They do wonders when they open up to others, but they seem to have a tendency to impose their worldviews.
- I’d encourage you to focus initially on organic ideas
- Now, this advice sounds more like the “scratch your own itch” advocation. But there’s a key difference in that it’s stated as part of a broader process. It’s more of a “walk before you run” or “do your homework” piece of advice, not a “you can’t come up with good ideas if you just think about how people will use your tool.”
- missing or broken
- It can cover a lot, but it’s couched in terms of the typical “problem-solving” approach at the centre of the engineering worldview. Since we’re talking about developing tools, it makes sense. But there could be a broader version, admitting for dreams, inspiration, aspiration. Not necessarily of the “what would make you happy?” kind, although there’s a lot to be said about happiness and imagination. You’re brainstorming, here.
- immediate answers
- Which might imply that there’s a second step. If you keep asking yourself the same question, you may be able to get a very large number of ideas. The second step could be to prioritize them but I prefer “outlining” as a process: you shuffle things together and you group some ideas to get one which covers several. What’s common between your need for a simpler way to code on the Altair and your values? Why do you care so much about algorithms instead of human encoding?
- You may need to stand outside yourself a bit to see brokenness
- Ah, yes! “Taking a step back,” “distancing yourself,” “seeing the forest for the trees”… A core dimension of the ethnographic approach and the need for a back-and-forth between “inside” and “outside.” There’s a reflexive component in this “being an outsider to yourself.” It’s not only psychological, it’s a way to get into the social, which can lead to broader success if it’s indeed not just about scratching your own itch.
- get used to it and take it for granted
- That’s enculturation, to you. When you do things a certain way simply because “we’ve always done them that way,” you may not create these organic ideas. But it’s a fine way to do your work. Asking yourself important questions about what’s wrong with your situation works well in terms of getting new ideas. But, sometimes, you need to get some work done.
- a Facebook
- Yet another recontextualized example. Zuckerberg wasn’t trying to solve that specific brokenness, as far as we know. But Facebook became part of what it is when Zuck began scratching that itch.
- organic startup ideas usually don’t
seem like startup ideas at first
- Which gets us to the pivotal importance of working with others. Per this article, VCs and “angel investors,” probably. But, in the case of some of cases cited, those we tend to forget, like Paul Allen, Narendra, and the Winklevosses.
- end up making
something of value to a lot of people
- Trial and error, it’s an iterative process. So you must recognize errors quickly and not invest too much effort in a specific brokenness. Part of this requires maturity.
other people dismiss as a toy
- The passage on which Gruber focused and an interesting tidbit. Not that central, come to think of it. But it’s important to note that people’s dismissive attitude may be misled, that “toys” may hide tools, that it’s probably a good idea not to take all feedback to heart…
- At this point, when someone comes to us with
something that users like but that we could envision forum trolls
dismissing as a toy, it makes us especially likely to invest.
- the best source of organic ones
- Especially to investors. Potentially self-serving… in a useful way.
- they’re at the forefront of technology
- That part I would dispute, actually. Unless we talk about a specific subgroup of young founders and a specific set of tools. Young founders tend to be oblivious to a large field in technology, including social tools.
- they’re in a position to discover
valuable types of fixable brokenness first
- The focus on fixable brokenness makes sense if we’re thinking exclusively through the engineering worldview, but it’s at the centre of some failures like the Google Buzz launch.
- you still have to work hard
- Of the “inspiration shouldn’t make use forget perspiration” kind. Makes for a more thoughtful approach than the frequent “all you need to do…” claims.
- I’d encourage anyone
starting a startup to become one of its users, however unnatural it
- Not merely an argument for dogfooding. It’s deeper than that. Googloids probably use Google tools but they didn’t actually become users. They’re beta testers with a strong background in troubleshooting. Not the best way to figure out what users really want or how the tool will ultimately fail.
- It’s hard to compete directly with open source software
- Open Source as competition isn’t new as a concept, but it takes time to seep in.
- there has to be some part
you can charge for
- The breach through which old-school “business models” enter with little attention paid to everything else. To the extent that much of the whole piece might crumble from pressure built up by the “beancounter” worldview. Good thing he acknowledges it.
Category Archives: gadgets
[Jump here for more technical details.]
A few months ago, I installed BuddyPress on my Mac to try it out. It was a bit of an involved process, so I documented it:
More recently, I decided to get a webhost. Both to run some tests and, eventually, to build something useful. BuddyPress seems like a good way to go at it, especially since it’s improved a lot, in the past several months.
In fact, the installation process is much simpler, now, and I ran into some difficulties because I was following my own instructions (though adapting the process to my webhost). So a new blogpost may be in order. My previous one was very (possibly too) detailed. This one is much simpler, technically.
One thing to make clear is that BuddyPress is a set of plugins meant for WordPress µ (“WordPress MU,” “WPMU,” “WPµ”), the multi-user version of the WordPress blogging platform. BP is meant as a way to make WPµ more “social,” with such useful features as flexible profiles, user-to-user relationships, and forums (through bbPress, yet another one of those independent projects based on WordPress).
While BuddyPress depends on WPµ and does follow a blogging logic, I’m thinking about it as a social platform. Once I build it into something practical, I’ll probably use the blogging features but, in a way, it’s more of a tool to engage people in online social activities. BuddyPress probably doesn’t work as a way to “build a community” from scratch. But I think it can be quite useful as a way to engage members of an existing community, even if this engagement follows a blogger’s version of a Pareto distribution (which, hopefully, is dissociated from elitist principles).
But I digress, of course. This blogpost is more about the practical issue of adding a BuddyPress installation to a webhost.
Webhosts have come a long way, recently. Especially in terms of shared webhosting focused on LAMP (or PHP/MySQL, more specifically) for blogs and content-management. I don’t have any data on this, but it seems to me that a lot of people these days are relying on third-party webhosts instead of relying on their own servers when they want to build on their own blogging and content-management platforms. Of course, there’s a lot more people who prefer to use preexisting blog and content-management systems. For instance, it seems that there are more bloggers on WordPress.com than on other WordPress installations. And WP.com blogs probably represent a small number of people in comparison to the number of people who visit these blogs. So, in a way, those who run their own WordPress installations are a minority in the group of active WordPress bloggers which, itself, is a minority of blog visitors. Again, let’s hope this “power distribution” not a basis for elite theory!
Yes, another digression. I did tell you to skip, if you wanted the technical details!
I became part of the “self-hosted WordPress” community through a project on which I started work during the summer. It’s a website for an academic organization and I’m acting as the organization’s “Web Guru” (no, I didn’t choose the title). The site was already based on WordPress but I was rebuilding much of it in collaboration with the then-current “Digital Content Editor.” Through this project, I got to learn a lot about WordPress, themes, PHP, CSS, etc. And it was my first experience using a cPanel- (and Fantastico-)enabled webhost (BlueHost, at the time). It’s also how I decided to install WordPress on my local machine and did some amount of work from that machine.
But the local installation wasn’t an ideal solution for two reasons: a) I had to be in front of that local machine to work on this project; and b) it was much harder to show the results to the person with whom I was collaborating.
So, in the Fall, I decided to get my own staging server. After a few quick searches, I decided HostGator, partly because it was available on a monthly basis. Since this staging server was meant as a temporary solution, HG was close to ideal. It was easy to set up as a PayPal “subscription,” wasn’t that expensive (9$/month), had adequate support, and included everything that I needed at that point to install a current version of WordPress and play with theme files (after importing content from the original site). I’m really glad I made that decision because it made a number of things easier, including working from different computers, and sending links to get feedback.
While monthly HostGator fees were reasonable, it was still a more expensive proposition than what I had in mind for a longer-term solution. So, recently, a few weeks after releasing the new version of the organization’s website, I decided to cancel my HostGator subscription. A decision I made without any regret or bad feeling. HostGator was good to me. It’s just that I didn’t have any reason to keep that account or to do anything major with the domain name I was using on HG.
Though only a few weeks elapsed since I canceled that account, I didn’t immediately set out to transition to a new webhost. I didn’t go from HostGator to another webhost.
But having my own webhost still remained at the back of my mind as something which might be useful. For instance, while not really making a staging server necessary, a new phase in the academic website project brought up a sandboxing idea. Also, I went to a “WordPress Montreal” meeting and got to think about further WordPress development/deployment, including using BuddyPress for my own needs (both as my own project and as a way to build my own knowledge of the platform) instead of it being part of an organization’s project. I was also thinking about other interesting platforms which necessitate a webhost.
(More on these other platforms at a later point in time. Bottom line is, I’m happy with the prospects.)
So I wanted a new webhost. I set out to do some comparison shopping, as I’m wont to do. In my (allegedly limited) experience, finding the ideal webhost is particularly difficult. For one thing, search results are cluttered with a variety of “unuseful” things such as rants, advertising, and limited comparisons. And it’s actually not that easy to give a new webhost a try. For one thing, these hosting companies don’t necessarily have the most liberal refund policies you could imagine. And, switching a domain name between different hosts and registrars is a complicated process through which a name may remain “hostage.” Had I realized what was involved, I might have used a domain name to which I have no attachment or actually eschewed the whole domain transition and just try the webhost without a dedicated domain name.
At any rate, I had a relatively hard time finding my webhost.
I really didn’t need “bells and whistles.” For instance, all the AdSense, shopping cart, and other business-oriented features which seem to be publicized by most webhosting companies have no interest, to me.
I didn’t even care so much about absolute degree of reliability or speed. What I’m to do with this host is fairly basic stuff. The core idea is to use my own host to bypass some limitations. For instance, WordPress.com doesn’t allow for plugins yet most of the WordPress fun has to do with plugins.
I did want an “unlimited” host, as much as possible. Not because expect to have huge resource needs but I just didn’t want to have to monitor bandwidth.
I thought that my needs would be basic enough that any cPanel-enabled webhost would fit. As much as I could see, I needed FTP access to something which had PHP 5 and MySQL 5. I expected to install things myself, without use of the webhost’s scripts but I also thought the host would have some useful scripts. Although I had already registered the domain I wanted to use (through Name.com), I thought it might be useful to have a free domain in the webhosting package. Not that domain names are expensive, it’s more of a matter of convenience in terms of payment or setup.
I ended up with FatCow. But, honestly, I’d probably go with a different host if I were to start over (which I may do with another project).
I paid 88$ for two years of “unlimited” hosting, which is quite reasonable. And, on paper, FatCow has everything I need (and I bunch of things I don’t need). The missing parts aren’t anything major but have to do with minor annoyances. In other words, no real deal-breaker, here. But there’s a few things I wish I had realized before I committed on FatCow with a domain name I actually want to use.
Something which was almost a deal-breaker for me is the fact that FatCow requires payment for any additional subdomain. And these aren’t cheap: the minimum is 5$/month for five subdomains, up to 25$/month for unlimited subdomains! Even at a “regular” price of 88$/year for the basic webhosting plan, the “unlimited subdomains” feature (included in some webhosting plans elsewhere) is more than three times more expensive than the core plan.
As I don’t absolutely need extra subdomains, this is mostly a minor irritant. But it’s one reason I’ll probably be using another webhost for other projects.
Other issues with FatCow are probably not enough to motivate a switch.
For instance, the PHP version installed on FatCow (5.2.1) is a few minor releases behind the one needed by some interesting web applications. No biggie, especially if PHP is updated in a relatively reasonable timeframe. But still makes for a slight frustration.
The MySQL version seems recent enough, but it uses non-standard tools to manage it, which makes for some confusion. Attempting to create some MySQL databases with obvious names (say “wordpress”) fails because the database allegedly exists (even though it doesn’t show up in the MySQL administration). In the same vein, the URL of the MySQL is <username>.fatcowmysql.com instead of localhost as most installers seem to expect. Easy to handle once you realize it, but it makes for some confusion.
In terms of Fantastico-like simplified installation of webapps, FatCow uses InstallCentral, which looks like it might be its own Fantastico replacement. InstallCentral is decent enough as an installation tool and FatCow does provide for some of the most popular blog and CMS platforms. But, in some cases, the application version installed by FatCow is old enough (2005!) that it requires multiple upgrades to get to a current version. Compared to other installation tools, FatCow’s InstallCentral doesn’t seem really efficient at keeping track of installed and released versions.
Something which is partly a neat feature and partly a potential issue is the way FatCow handles Apache-related security. This isn’t something which is so clear to me, so I might be wrong.
Accounts on both BlueHost and HostGator include a public_html directory where all sorts of things go, especially if they’re related to publicly-accessible content. This directory serves as the website’s root, so one expects content to be available there. The “index.html” or “index.php” file in this directory serves as the website’s frontpage. It’s fairly obvious, but it does require that one would understand a few things about webservers. FatCow doesn’t seem to create a public_html directory in a user’s server space. Or, more accurately, it seems that the root directory (aka ‘/’) is in fact public_html. In this sense, a user doesn’t have to think about which directory to use to share things on the Web. But it also means that some higher-level directories aren’t available. I’ve already run into some issues with this and I’ll probably be looking for a workaround. I’m assuming there’s one. But it’s sometimes easier to use generally-applicable advice than to find a custom solution.
Further, in terms of access control… It seems that webapps typically make use of diverse directories and .htaccess files to manage some forms of access controls. Unix-style file permissions are also involved but the kind of access needed for a web app is somewhat different from the “User/Group/All” of Unix filesystems. AFAICT, FatCow does support those .htaccess files. But it has its own tools for building them. That can be a neat feature, as it makes it easier, for instance, to password-protect some directories. But it could also be the source of some confusion.
There are other issues I have with FatCow, but it’s probably enough for now.
It only takes a few minutes and is rather straightforward. This is the most verbose version of that process you could imagine…
Disclaimer: I’m mostly documenting how I did it and there are some things about which I’m unclear. So it may not work for you. If it doesn’t, I may be able to help but I provide no guarantee that I will. I’m an anthropologist, not a Web development expert.
As always, YMMV.
A few instructions here are specific to FatCow, but the general process is probably valid on other hosts.
I’m presenting things in a sequence which should make sense. I used a slightly different order myself, but I think this one should still work. (If it doesn’t, drop me a comment!)
In these instructions, straight quotes (“”) are used to isolate elements from the rest of the text. They shouldn’t be typed or pasted.
I use “example.com” to refer to the domain on which the installation is done. In my case, it’s the domain name I transfered to FatCow from another registrar but it could probably be done without a dedicated domain (in which case it would be “<username>.fatcow.com” where “<username>” is your FatCow username).
I started with creating a MySQL database for WordPress MU. FatCow does have phpMyAdmin but the default tool in the cPanel is labeled “Manage MySQL.” It’s slightly easier to use for creating new databases than phpMyAdmin because it creates the database and initial user (with confirmed password) in a single, easy-to-understand dialog box.
- WordPress MU (wordpress-mu-220.127.116.11.zip, in my case)
- Buddymatic (buddymatic.0.9.6.3.1.zip, in my case)
- EarlyMorning (only one version, it seems)
- EarlyMorning-BP (only one version, it seems)
Only the WordPress MU archive is needed to install BuddyPress. The last three files are needed for EarlyMorning, a BuddyPress theme that I found particularly neat. It’s perfectly possible to install BuddyPress without this specific theme. (Although, doing so, you need to install a BuddyPress-compatible theme, if only by moving some folders to make the default theme available, as I explained in point 15 in that previous tutorial.) Buddymatic itself is a theme framework which includes some child themes, so you don’t need to install EarlyMorning. But installing it is easy enough that I’m adding instructions related to that theme.
These files can be uploaded anywhere in my FatCow space. I uploaded them to a kind of test/upload directory, just to make it clear, for me.
A major FatCow idiosyncrasy is its FileManager (actually called “FileManager Beta” in the documentation but showing up as “FileManager” in the cPanel). From my experience with both BlueHost and HostGator (two well-known webhosting companies), I can say that FC’s FileManager is quite limited. One thing it doesn’t do is uncompress archives. So I have to resort to the “Archive Gateway,” which is surprisingly slow and cumbersome.
At any rate, I used that Archive Gateway to uncompress the four files. WordPress µ first (in the root directory or “/”), then both Buddymatic and EarlyMorning in “/wordpress-mu/wp-content/themes” (you can chose the output directory for zip and tar files), and finally EarlyMorning-BP (anywhere, individual files are moved later). To uncompress each file, select it in the dropdown menu (it can be located in any subdirectory, Archive Gateway looks everywhere), add the output directory in the appropriate field in the case of Buddymatic or EarlyMorning, and press “Extract/Uncompress”. Wait to see a message (in green) at the top of the window saying that the file has been uncompressed successfully.
Then, in the FileManager, the contents of the EarlyMorning-BP directory have to be moved to “/wordpress-mu/wp-content/themes/earlymorning”. (Thought they could be uncompressed there directly, but it created an extra folder.) To move those files in the FileManager, I browse to that earlymorning-bp directory, click on the checkbox to select all, click on the “Move” button (fourth from right, marked with a blue folder), and add the output path: /wordpress-mu/wp-content/themes/earlymorning
These files are tweaks to make the EarlyMorning theme work with BuddyPress.
Then, I had to change two files, through the FileManager (it could also be done with an FTP client).
One change is to EarlyMorning’s style.css:
There, “Template: thematic” has to be changed to “Template: buddymatic” (so, “the” should be changed to “buddy”).
That change is needed because the EarlyMorning theme is a child theme of the “Thematic” WordPress parent theme. Buddymatic is a BuddyPress-savvy version of Thematic and this changes the child-parent relation from Thematic to Buddymatic.
The other change is in the Buddymatic “extensions”:
There, on line 39, “$bp->root_domain” should be changed to “bp_root_domain()”.
This change is needed because of something I’d consider a bug but that a commenter on another blog was kind enough to troubleshoot. Without this modification, the login button in BuddyPress wasn’t working because it was going to the website’s root (example.com/wp-login.php) instead of the WPµ installation (example.com/wordpress-mu/wp-login.php). I was quite happy to find this workaround but I’m not completely clear on the reason it works.
Then, something I did which might not be needed is to rename the “wordpress-mu” directory. Without that change, the BuddyPress installation would sit at “example.com/wordpress-mu,” which seems a bit cryptic for users. In my mind, “example.com/<name>,” where “<name>” is something meaningful like “social” or “community” works well enough for my needs. Because FatCow charges for subdomains, the “<name>.example.com” option would be costly.
(Of course, WPµ and BuddyPress could be installed in the site’s root and the frontpage for “example.com” could be the BuddyPress frontpage. But since I think of BuddyPress as an add-on to a more complete site, it seems better to have it as a level lower in the site’s hierarchy.)
With all of this done, the actual WPµ installation process can begin.
The first thing is to browse to that directory in which WPµ resides, either “example.com/wordpress-mu” or “example.com/<name>” with the “<name>” you chose. You’re then presented with the WordPress µ Installation screen.
Since FatCow charges for subdomains, it’s important to choose the following option: “Sub-directories (like example.com/blog1).” It’s actually by selecting the other option that I realized that FatCow restricted subdomains.
An important FatCow-specific point, here, is that “Database Host” should be “<username>.fatcowmysql.com” (where “<username>” is your FatCow username). In my experience, other webhosts use “localhost” and WPµ defaults to that.
You’re asked to give a name to your blog. In a way, though, if you think of BuddyPress as more of a platform than a blogging system, that name should be rather general. As you’re installing “WordPress Multi-User,” you’ll be able to create many blogs with more specific names, if you want. But the name you’re entering here is for BuddyPress as a whole. As with <name> in “example.com/<name>” (instead of “example.com/wordpress-mu”), it’s a matter of personal opinion.
Something I noticed with the EarlyMorning theme is that it’s a good idea to keep the main blog’s name relatively short. I used thirteen characters and it seemed to fit quite well.
Once you’re done filling in this page, WPµ is installed in a flash. You’re then presented with some information about your installation. It’s probably a good idea to note down some of that information, including the full paths to your installation and the administrator’s password.
But the first thing you should do, as soon as you log in with “admin” as username and the password provided, is probably to the change that administrator password. (In fact, it seems that a frequent advice in the WordPress community is to create a new administrator user account, with a different username than “admin,” and delete the “admin” account. Given some security issues with WordPress in the past, it seems like a good piece of advice. But I won’t describe it here. I did do it in my installation and it’s quite easy to do in WPµ.
Then, you should probably enable plugins here:
(From what I understand, it might be possible to install BuddyPress without enabling plugins, since you’re logged in as the administrator, but it still makes sense to enable them and it happens to be what I did.)
You can also change a few other options, but these can be set at another point.
One option which is probably useful, is this one:
|Allow new registrations|| Disabled
Enabled. Blogs and user accounts can be created.
Only user account can be created.
Obviously, it’s not necessary. But in the interest of opening up the BuddyPress to the wider world without worrying too much about a proliferation of blogs, it might make sense. You may end up with some fake user accounts, but that shouldn’t be a difficult problem to solve.
Now comes the installation of the BuddyPress plugin itself. You can do so by going here:
And do a search for “BuddyPress” as a term. The plugin you want was authored by “The BuddyPress Community.” (In my case, version 1.1.3.) Click the “Install” link to bring up the installation dialog, then click “Install Now” to actually install the plugin.
Once the install is done, click the “Activate” link to complete the basic BuddyPress installation.
You now have a working installation of BuddyPress but the BuddyPress-savvy EarlyMorning isn’t enabled. So you need to go to “example.com/<name>/wp-admin/wpmu-themes.php” to enable both Buddymatic and EarlyMorning. You should then go to “example.com/<name>/wp-admin/themes.php” to activate the EarlyMorning theme.
Something which tripped me up because it’s now much easier than before is that forums (provided through bbPress) are now, literally, a one-click install. If you go here:
Besides this, I’d advise that you set up a few widgets for the BuddyPress frontpage. You do so through an easy-to-use drag-and-drop interface here:
I especially advise you to add the Twitter RSS widget because it seems to me to fit right in. If I’m not mistaken, the EarlyMorning theme contains specific elements to make this widget look good.
After that, you can just have fun with your new BuddyPress installation. The first thing I did was to register a new user. To do so, I logged out of my admin account, and clicked on the Sign Up button. Since I “allow new registrations,” it’s a very simple process. In fact, this is one place where I think that BuddyPress shines. Something I didn’t explain is that you can add a series of fields for that registration and the user profile which goes with it.
The whole process really shouldn’t take very long. In fact, the longest parts have probably to do with waiting for Archive Gateway.
The rest is “merely” to get people involved in your BuddyPress installation. It can happen relatively easily, if you already have a group of people trying to do things together online. But it can be much more complicated than any software installation process… 😉
3 Comments | tags: #wpmtl, .htaccess, .htaccess Editor, Apache, Archive Gateway, bbPress, blog name, BlueHost, Buddymatic, BuddyPress, BuddyPress themes, building websites, business features, child themes, cloud computing, comparison shopping, content management, cPanel, CyberDuck, digressions, domain names, EarlyMorning, elite theory, extended profiles, Fantastico, FatCow, FatCow issues, FatCow problems, FatCow review, FatCow woes, FatCow.com, fatcowmysql.com, FileManager, FileManager Beta, FileZilla, forum software, forums, friendship, Google AdSense, HostGator, HostGator Subscription, InstallCentral, LAMP, Manage MySQL, MySQL 5, open registrations, Pareto Principle, personal projects, PHP 5, PHP MySQL, phpMyAdmin, public_html, sandboxes, social features, staging servers, statistical minority, subdomains, troubleshooting, Tutorials, Twitter RSS, unlimited webhosting, verbose, verbosity, web development, webhosting companies, webhosts, Websites, WordPress µ, WordPress Montreal, WordPress MU, WordPress plugins, WordPress security, WordPress.org, WPµ, WPMU | posted in Blogging, blogging systems, blogging tools, blogosphere, Clueing, comment-fishing, comments, Communities, community-building, Content Management Systems, development, Digital Life, digital lifestyle, experience, experimentation, free software, gadgets, geek crowd, geekness, geeks, learn by doing, musings, new media, online communication, online communities, online publishing, Open Source Movement, open-source, participatory culture, ramblings, rants, social networking, social networks, social publishing, social software, software, Tech, Web applications, WordPress, WordPress.com, workflow
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.
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.
Leave a comment | tags: cloud computing, killer apps, personal devices, social media, Touch devices, wearable computing | posted in cellphones, Crazy Predictions, gadgets, getting things done, iPhone, iPod touch, PDAs, personal, professionals, quickies, ramblings, smartphones, soapbox, speech recognition, techno enthusiasts, techno lust, voice, voice interface, wishful thinking, wishlists, writing
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.
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.
2 Comments | tags: Address Book.app, App Store, Apple tablet, Apple Touch, Creative, Creative Labs, Dasher, dictation, eMate, EndNote, eWorld, handwriting recognition, iChat Mobile, input method, iPad, iPod touch, ISI, keyboard, logbook, mac, media annotation, MessagEase, MessagePad, MobileMe, OLPC XOXO, podcast synchronization, RefWorks, Revver, Safari Pad, sharing app, Soundcloud, speech recognition, Tablet Mac, text entry, text input, Touch devices, XOXO, Zii, Zii EGG, Zotero | posted in A, Apple, Crazy Predictions, Education, enhanced podcast, enthusiasm, gadgets, iPhone, iPod, iPod touch, iTunes, Learning, lecturecasts, mac, mac os x, music, musings, OLPC, One Laptop Per Child, optimism, PDAs, Placeholders, podcasting, predictions, quickies, shameless plug, smartphones, techno enthusiasts, techno lust, technology, wishful thinking, writing
Today, I’m buying an old Mac mini G4 1.25GHz. Yes, a low end computer from 2005. It’ll be great to be back in Mac after spending most of my computer life on XP for three years.
This mini is slower than my XP desktop (emachines H3070). But that doesn’t really matter for what I want to do.
There’s something to be said about computers being “fast enough.” Gamers and engineers may not grok this concept, since they always want more. But there’s a point at which computers don’t really need to be faster, for some categories of uses.
Car analogies are often made, in computer discussions, and this case seems fairly obvious. Some cars are still designed to “push the envelope,” in terms of performance. Yet most cars, including some relatively inexpensive ones, are already fast enough to run on highways beyond the speed limits in North America. Even in Europe, most drivers don’t tend to push their cars to the limit. Something vaguely similar happens with computers, though there are major differences. For instance, the difference in cost between fast driving and normal driving is a factor with cars while it isn’t so much of a factor with computers. With computers, the need for cooling and battery power (on laptops) do matter but, even if they were completely solved, there’s a limit to the power needed for casual computer use.
This isn’t contradicting Moore’s Law directly. Chips do increase exponentially in speed-to-cost ratio. But the effects aren’t felt the same way through all uses of computers, especially if we think about casual use of desktop and laptop “personal computers.” Computer chips in other devices (from handheld devices to cars or DVD players) benefit from Moore’s Law, but these are not what we usually mean by “computer,” in daily use.
The common way to put it is something like “you don’t need a fast machine to do email and word processing.”
The main reason I needed a Mac is that I’ll be using iMovie to do simple video editing. Video editing does push the limits of a slow computer and I’ll notice those limits very readily. But it’ll still work, and that’s quite interesting to think about, in terms of the history of personal computing. A Mac mini G4 is a slug, in comparison with even the current Mac mini Core 2 Duo. But it’s fast enough for even some tasks which, in historical terms, have been processor-intensive.
None of this is meant to say that the “need for speed” among computer users is completely manufactured. As computers become more powerful, some applications of computing technologies which were nearly impossible at slower speeds become easy to do. In fact, there certainly are things which we don’t even imagine becoming which will be easy to do in the future, thanks to improvements in computer chip performance. Those who play processor-intensive games always want faster machines and they certainly feel the “need for speed.” But, it seems to me, the quest for raw speed isn’t the core of personal computing, anymore.
This all reminds me of the Material Culture course I was teaching in the Fall: the Social Construction of Technology, Actor-Network Theory, the Social Shaping of Technology, etc.
So, a low end computer makes sense.
While iMovie is the main reason I decided to get a Mac at this point, I’ve been longing for Macs for three years. There were times during which I was able to use somebody else’s Mac for extended periods of time but this Mac mini G4 will be the first Mac to which I’ll have full-time access since late 2005, when my iBook G3 died.
As before, I’m happy to be “back in Mac.” I could handle life on XP, but it never felt that comfortable and I haven’t been able to adapt my workflow to the way the Windows world works. I could (and probably should) have worked on Linux, but I’m not sure it would have made my life complete either.
Some things I’m happy to go back to:
- Nisus Thesaurus
- Address Book
- TAMS Analyzer
Now I need to install some RAM in this puppy.
1 Comment | tags: Actor-Network Theory, Address Book.app, BibDesk, car analogies, clock speed, computer chips, Core 2 Duo, Dictionary.app, emachines, embedded devices, G4, GarageBand (software), Good Enough, iCal, iChat, iLife, iMovie, iWork, Keynote (software), low end mac, Mac mini, Mail.app, material culture, Moore's Law, Nisus Thesaurus, OmniOutliner, personal computers, PowerPC G4, Preview.app, QuickSilver, Social Construction of Technology, Social Shaping of Technology, TAMS Analyzer, Terminal.app, TextEdit, XP | posted in Apple, comment-fishing, computers, constructivism, consumerism, consumption, Digital Life, digital lifestyle, gadgets, geek culture, mac, mac os x, personal, ramblings, shameless plug, soapbox, social change, Tech, techno enthusiasts, techno lust, technological determinism, technology, wishful thinking
I keep getting ideas for apps I’d like to see on Apple’s App Store for iPod touch and iPhone. This one may sound a bit weird but I think it could be fun. An app where you can record your mood and optionally broadcast it to friends. It could become rather sophisticated, actually. And I think it can have interesting consequences.
The idea mostly comes from Philippe Lemay, a psychologist friend of mine and fellow PDA fan. Haven’t talked to him in a while but I was just thinking about something he did, a number of years ago (in the mid-1990s). As part of an academic project, Philippe helped develop a PDA-based research program whereby subjects would record different things about their state of mind at intervals during the day. Apart from the neatness of the data gathering technique, this whole concept stayed with me. As a non-psychologist, I personally get the strong impression that recording your moods frequently during the day can actually be a very useful thing to do in terms of mental health.
And I really like the PDA angle. Since I think of the App Store as transforming Apple’s touch devices into full-fledged PDAs, the connection is rather strong between Philippe’s work at that time and the current state of App Store development.
Since that project of Philippe’s, a number of things have been going on which might help refine the “happy meter” concept.
One is that “lifecasting” became rather big, especially among certain groups of Netizens (typically younger people, but also many members of geek culture). Though the lifecasting concept applies mostly to video streams, there are connections with many other trends in online culture. The connection with vidcasting specifically (and podcasting generally) is rather obvious. But there are other connections. For instance, with mo-, photo-, or microblogging. Or even with all the “mood” apps on Facebook.
Speaking of Facebook as a platform, I think it meshes especially well with touch devices.
So, “happy meter” could be part of a broader app which does other things: updating Facebook status, posting tweets, broadcasting location, sending personal blogposts, listing scores in a Brain Age type game, etc.
Yet I think the “happy meter” could be useful on its own, as a way to track your own mood. “Turns out, my mood was improving pretty quickly on that day.” “Sounds like I didn’t let things affect me too much despite all sorts of things I was going through.”
As a mood-tracker, the “happy meter” should be extremely efficient. Because it’s easy, I’m thinking of sliders. One main slider for general mood and different sliders for different moods and emotions. It would also be possible to extend the “entry form” on occasion, when the user wants to record more data about their mental state.
Of course, everything would be save automatically and “sent to the cloud” on occasion. There could be a way to selectively broadcast some slider values. The app could conceivably send reminders to the user to update their mood at regular intervals. It could even serve as a “break reminder” feature. Though there are limitations on OSX iPhone in terms of interapplication communication, it’d be even neater if the app were able to record other things happening on the touch device at the same time, such as music which is playing or some apps which have been used.
Now, very obviously, there are lots of privacy issues involved. But what social networking services have taught us is that users can have pretty sophisticated notions of privacy management, if they’re given the chance. For instance, adept Facebook users may seem to indiscrimately post just about everything about themselves but are often very clear about what they want to “let out,” in context. So, clearly, every type of broadcasting should be controlled by the user. No opt-out here.
I know this all sounds crazy. And it all might be a very bad idea. But the thing about letting my mind wander is that it helps me remain happy.
4 Comments | tags: app ideas, App Store, biorhythms, Brain Age, cloud computing, cognitive psychology, crazy ideas, dangerous ideas, happiness, happy meter, lifecasting, livejournal, mental health, mental hygiene, mental states, microblogging, moods, PDAs, Philippe Lemay, privacy management, psychology, social psychology, Touch devices, Twitter, vidcasting | posted in Blogging, bonheur, cluefulness, constructivism, Crazy Predictions, digital lifestyle, douceur de vivre, Empowerment, enthusiasm, Facebook, fun, gadgets, geek crowd, geekness, iPhone, iPod touch, joie de vivre, location-specific, naïve, naïveté, online privacy, participatory culture, performance, personal life, playfulness, pleasure, podcasting, qualitative research, ramblings, smartphones, sophistication, tagging, trusting people, wishful thinking, wishlists, workflow
Took me a while before I watched this concept video about iPhone use on campus.
Sure, it’s a bit campy. Sure, some features aren’t available on the iPhone yet. But the basic concepts are pretty much what I had in mind.
Among things I like in the video:
- The very notion of student empowerment runs at the centre of it.
- Many of the class-related applications presented show an interest in the constructivist dimensions of learning.
- Material is made available before class. Face-to-face time is for engaging in the material, not rehashing it.
- The technology is presented as a way to ease the bureaucratic aspects of university life, relieving a burden on students (and, presumably, on everyone else involved).
- The “iPhone as ID” concept is simple yet powerful, in context.
- Social networks (namely Facebook and MySpace, in the video) are embedded in the campus experience.
- Blended learning (called “hybrid” in the video) is conceived as an option, not as an obligation.
- Use of the technology is specifically perceived as going beyond geek culture.
- The scenarios (use cases) are quite realistic in terms of typical campus life in the United States.
- While “getting an iPhone” is mentioned as a perk, it’s perfectly possible to imagine technology as a levelling factor with educational institutions, lowering some costs while raising the bar for pedagogical standards.
- The shift from “eLearning” to “mLearning” is rather obvious.
- ACU already does iTunes U.
- The video is released under a Creative Commons license.
Of course, there are many directions things can go, from here. Not all of them are in line with the ACU dream scenario. But I’m quite hope judging from some apparently random facts: that Apple may sell iPhones through universities, that Apple has plans for iPhone use on campuses, that many of the “enterprise features” of iPhone 2.0 could work in institutions of higher education, that the Steve Jobs keynote made several mentions of education, that Apple bundles iPod touch with Macs, that the OLPC XOXO is now conceived more as a touch handheld than as a laptop, that (although delayed) Google’s Android platform can participate in the same usage scenarios, and that browser-based computing apparently has a bright future.
6 Comments | tags: Abilene Christian University, blended learning, bureaucracy, Creative Commons, educational iPhone, Facebook, iPhone as ID, iPhone University, iTunes U, mLearning, mobile computing, Mobile Learning, university life | posted in academic institutions, academic podcasting, Apple, cluefulness, collaborative learning, college life, constructivism, course management systems, digital lifestyle, Education, education systems, eLearning, Empowerment, enthusiasm, gadget freaks, gadgets, geekness, globalization, informal learning, Institutions, iPhone, iPod touch, iTunes Wi-Fi Music Store, learn by doing, learners, learning materials, localization, location-specific, mac, MySpace, OLPC, open access, optimism, smartphones, soapbox, social change, social contract, social networks, teaching and learning, techno enthusiasts, textbooks, tributes, tuition fees, Universities, Web applications, wishful thinking, wishlists, workflow
Been thinking about blogging on my use of Personal Digital Assistants (PDAs) for a little while. Here’s my chance:
There’s simply no market these days for the traditional PDA, as even basic mobile phones can do everything a PDA can do, just with more style. Report: Apple developing OS X minitablet | One More Thing – CNET News.com
Uh-oh! No you didn’t! Well, Steve Jobs made a similar statement a long time ago so it’s not like you’re the first one to say it. But you’re still wrong!
(This blog entry will be choppier than usual. Should have posted this as a comment. But this is getting longer than I expected and I prefer trackbacks anyway.)
Not exactly sure where people in the Bay Area get the impression that there is no market for the traditional PDA. In my mind, the potential market for “the traditional PDA” is underestimated because the ideal PDA has yet to be released. No, the current crop of smartphones aren’t it.
Having said this, I do think cellphones have the brightest future of pretty much any other electronic device type, but I don’t agree that any cellphone currently does what a PDA can do. So, while I think the ideal portable device would likely be a cellphone, I’d like to focus on what a PDA really is.
While it’s clear that PDAs have had a tortuous history since the first Newton and Magic Cap devices were released, other tools haven’t completely obliterated the need for PDAs. Hence the “cult following” for Newton Message Pads and the interest in new generations of PDA-like devices.
One thing to keep in mind is that PDAs are not merely PIMs (personal information managers, typically focusing on contacts and calendars). Instead of a glorified organiser, a PDA is a complete computer with a focus on personal data. And people do care about personal data in computing.
Now, a disclaimer of sorts: I’ve been an active PDA user for a number of years. When I don’t have a PDA, I almost feel like something is missing from my life.
I have been taken by the very concept of PDAs the first time I saw an article on Apple’s Newton devices in a mainstream U.S. newspaper, way back in the early 1990s. I was dreaming of all the possibilities. And longed for my own Newton MessagePad.
I received a MessagePad 130 from Apple a few years later, having done some work for them. Used that Newton for a while and really enjoyed the experience. While human beings find my handwriting extremely difficult to read, my Newton MP130 did a fairly good job at recognising it. And having installed a version of Graffiti, I was able to write rather quickly on the device. The main issue I had with Newton devices was size. The MP was simply too bulky for me to carry around everywhere. I eventually stopped using the MP after a while, but was missing the convenience of my MP130.
I started using that Newton again in 2001, as I was preparing for fieldwork. Because I didn’t have a parallel port on the iBook I was getting for fieldwork, I also bought a Handspring Visor Deluxe. The Visor became a very valuable tool during my fieldwork trip to Mali, in 2002. IIRC, this model had already been discontinued but I had no trouble using it or finding new software for it. I used the Visor to take copious amounts of data which I was able to periodically transfer to my iBook. The fact that the Visor ran on standard batteries was definitely an asset in the field but I did lose data on occasion because, unlike Newton devices, Palm devices didn’t have persistent memory storage.
Coming back from Mali, I bought my first Sony Clié. I pretty much stuck with Cliés ever since and have been quite happy with them. Cliés have a few advantages over other PalmOS devices like MemorySticks and the jog dial. The form factor and screen resolution of an entry-level Clié were much better than those of my old Visor. Sony has discontinued sales of its Clié devices outside of Japan. Some used Cliés go for 30$ on eBay.
So, what do I do with a PDA? Actually, the main thing really is taking notes. Reading notes, research notes, lecture notes, conference notes, etc. I’ve taken notes on coffee I’ve tried, on things I’d like to learn, on moments I want to write more extensively about… Though my fingers are rather small, typing on a small QWERTY keyboard has never been a real option for me. I tried using the keyboard on a Clié NX70V and it wasn’t nearly as efficient as using Graffiti. In fact, I’ve become quite adept at MessagEase. I can usually take elaborate notes in real time and organise them as I wish. Some notes remain as snippets while other notes become part of bigger pieces, including much of what I’ve written in the past ten years.
I also use my PDA for a number of “simpler” things like converting units (volume and temperature, especially), playing games (while waiting for something or while listening to podcasts), setting different timers, planning trips on public transportation systems, etc. I used to try and use more PDA applications than I do now but I still find third party applications an important component of any real PDA.
I always wanted to have a WiFi-enabled PDA. It’s probably the main reason behind my original reaction to the iPod touch launch. With a good input system and a semi-ubiquitous WiFi connection, a WiFi-enabled PDA could be a “dream come true,” for me. Especially in terms of email, blogging, and social networking. Not to mention simple Web queries.
I do have a very clear idea in mind as to what would be my ideal PDA. I don’t need it to be an MP3 player, a gaming console, or a phone. I don’t really want it to have a qwerty keyboard or a still camera. I don’t even care so much about it having a colour screen. But it should have an excellent battery life, a small size, good synchronisation features, third party apps, persistent memory, a very efficient input system, and a user community. I dream of it having a high-quality sound recorder, a webcam (think videoconferencing), large amounts of memory, and a complete set of voice features perfectly tuned to its owner’s voice (like voice activation and speaker-dependent, continuous speech recognition). It could act as the perfect unit to store any kind of personal data as a kind of “smart thumbdrive.” It could be synchronised with almost any other machine without any loss of information. It would probably have GPS and location-enabled features. It could be used to drive other systems or act as the ultimate smartcard. And it should be inexpensive.
I personally think price is one of the main reasons the traditional PDA has had such a hard time building/reaching markets. Inexpensive PDAs tended to miss important features. The most interesting PDAs were as expensive as much more powerful computers. Surely, miniaturisation is costly and it never was possible for any company to release a really inexpensive yet full-featured PDA. So it may be accurate to say that the traditional PDA is too expensive for its potential market. I perceive a huge difference between problems associated with costs and the utter lack of any PDA market.
Price does tend to be a very important factor with computer technology. The OLPC project is a good example of this. While the laptop produced through this project has many other features, the one feature which caught most of the media attention was the expected price for the device, around USD$100. All this time, many people are thinking that the project should have been a cellphone project because cellphone penetration is already high and cellphones are already the perfect leapfrog tool.
So it’s unlikely that I will get my dream PDA any time soon. Chances are, I’ll end up having to use a smartphone with very few of the features I really want my PDA to have. But, as is my impression with the OLPC project, we still need to dream and talk about what these devices can be.
13 Comments | tags: cellphone, Clié, field research, gadgets, leapfrog, MessagEase, MessagePad, Newton, OLPC, PalmOS, PDA, personal digital assistant, portable device, predictions, smartphone, speech recognition, technology, tools, Visor, WiFi | posted in gadgets, PDAs, ramblings
- October 2013
- November 2012
- February 2012
- January 2011
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005