Menu

Posts tagged “technology”

Google Glass and driving our bodies around

John Pavlus in Your Body Does Not Want to Be an Interface:

The assumption driving these kinds of design speculations is that if you embed the interface — the control surface for a technology — into our own bodily envelope, that interface will “disappear”: the technology will cease to be a separate “thing” and simply become part of that envelope.

The trouble is that unlike technology, your body isn’t something you “interface” with in the first place. You’re not a little homunculus “in” your body, “driving” it around, looking out Terminator-style “through” your eyes. Your body isn’t a tool for delivering your experience: it is your experience. Merging the body with a technological control surface doesn’t magically transform the act of manipulating that surface into bodily experience. I’m not a cyborg (yet) so I can’t be sure, but I suspect the effect is more the opposite: alienating you from the direct bodily experiences you already have by turning them into technological interfaces to be manipulated. 

It’s an excellent essay. I especially like the distinction between Ready-at-hand and Present-at-hand technologies, and how our bodies shouldn’t become marionettes to technology.

Why big IT projects always go wrong

John Naughton wrote a good summary of the Mythical Man-Month problem (the belief that adding more people to a project will get it done faster) in Why big IT projects always go wrong:

Man-months are a hopeless metric for assessing the size of a complex software project. Why? Basically because a big software project involves two kinds of work: the actual writing of computer code; and co-ordinating the work of the dozens — or maybe hundreds — of programmers working on different parts of the overall system. Co-ordination represents an essential but unproductive overhead: and the more programmers you have, the bigger that overhead becomes. Hence Brooks’s law: adding manpower to a late software project makes it later.

I’ve yet to see a large project where this law doesn’t apply.

[Sponsor] Filepicker.io Cloud Connect APIs

Develop Smarter, Simpler and Better Connected Apps with Javascript

Imagine connecting your app to everything with just 2 lines of code — files from all over the web, across cloud storage source, social networks and devices.

Filepicker.io provides a full file system API for your web and mobile applications that allows your app to upload, open, read, write, store, sync and convert files from over 17 sources including Dropbox, Google Docs, Facebook, Skydrive and Box. With the Filepicker.io Javascript API, request a file and receive a simplified URL. Then, upload the URL to your server or serve through your CDN.

Filepicker.io includes a customizable drop-in UI widget and an API library allowing you to send uploaded files directly to your S3. Sign up for Filepicker.io today!

Filepicker

Sponsorship by The Syndicate.

Why we should be wary of highly targeted information and ads

In his post Why we fear Facebook and why we shouldn’t Paul Jacobson makes an interesting counterpoint to the common refrain that it’s bad to share our personal data with companies:

Conventional wisdom is that if you are not paying for a product, you are the product. That may be true, as a generalisation. I prefer to think it isn’t so much we who are the products on Facebook but rather our preferences and attention. What does that buy us? For starters, it buys us Facebook, Twitter, Google services and more. It also buys us slightly less annoying ads that can be remarkably relevant. It buys advertisers a better chance that we may want to buy their products and services because those products and services may just be what we are looking for at that point in time.

It’s a good question. Is it really that bad to get highly targeted ads in our news feeds? The more targeted the ads are, the more useful they are to us, right? So why is there such pushback against this trend in companies like Google and Facebook to try to find out everything they can about us?

I think there are three main reasons why we need to be wary of letting ad-driven companies know too much about our preferences, even if they just use it to serve us more targeted information and ads.

1. It makes the web smaller

If we only see stuff we’re already interested in, we run the risk of becoming sucked into the Internet’s “filter bubble”, where it’s much harder to discover new information beyond our current knowledge. Maria Popova puts it like this in Are We Becoming Cyborgs?:

The Web by and large is really well designed to help people find more of what they already know they’re looking for, and really poorly designed to help us discover that which we don’t yet know will interest us and hopefully even change the way we understand the world.

When an algorithmic constraint is placed on the information we see, and that constraint is based solely on our current preferences, we will remain safely locked into the world we know. That means that we become less likely to broaden our horizons with new discoveries.

2. It results in heightened confirmation bias

When we’re steeped in information that confirms our existing beliefs (regardless of whether those beliefs are true or not) we not only seek out more of the same information everywhere we go, but we also become incapable of changing our minds even if we eventually are presented with the truth (the denial of Global Warming is a good example of this…). This is called confirmation bias, and Clay Johnson writes about it in the context of media and the Internet in his book The Information Diet:

It’s too high of a cognitive and ego burden to surround ourselves with people that we disagree with. If you’re a Facebook user, try counting up the number of friends you have who share your political beliefs. Unless you’re working hard to do otherwise, it’s likely that you’ve surrounded yourself with people who skew towards your beliefs. Now look beyond political beliefs—how many of your friends share the same economic class as you? […]

Those algorithms are everywhere: our web searches, our online purchases, our advertisements. This network of predictions is what Pariser calls the Filter Bubble in his book by the same name—the network of personalization technology that figures out what you want and keeps feeding you that at the expense of what you don’t want.

So, for example, through its EdgeRank algorithm Facebook figures out what we like and what we believe in, and then shows us stories and ads that confirm those beliefs. It doesn’t care about truth, it cares about engagement — even if that engagement comes at the expense of what is right.

3. It designs our lives for us

This is true for all advertising, but even more so for hyper-targeted advertising: it tries to sell us stuff we don’t necessarily need. Yes, I know we’re tired of hearing how we should all live with less stuff blah blah blah. That’s not necessarily what I’m saying. What I’m saying is that we need to be careful that we don’t become a society built around the needs of corporations. David Cain talks about this in his chilling essay called Your Lifestyle Has Already Been Designed:

We’ve been led into a culture that has been engineered to leave us tired, hungry for indulgence, willing to pay a lot for convenience and entertainment, and most importantly, vaguely dissatisfied with our lives so that we continue wanting things we don’t have. We buy so much because it always seems like something is still missing. […]

The perfect customer is dissatisfied but hopeful, uninterested in serious personal development, highly habituated to the television, working full-time, earning a fair amount, indulging during their free time, and somehow just getting by.

There’s nothing wrong with stuff, of course. But there is something scarily wrong about the way we let our desires be dictated by advertising — especially targeted advertising by companies that know us so well.

What it means…

I don’t think our biggest fears about the data that companies collect about us should revolve around identity theft or the government coming to get us (although, in some regions, that’s certainly legitimate concerns). Our biggest fear should be what Huxley points to in the future he paints in Brave New World: that we will be ruled by what he calls “man’s almost infinite appetite for distractions”. Huxley believed we should fear companies who aim to control us by inflicting pleasure on us, and I think he might have been on to something.

I know that sounds really alarmist. But still, I can’t look at my Facebook news feed and not think about this possible future. That’s why I think we should hold our personal data and preferences just a little bit closer to our hearts.

Responsive Web Design in Africa: why it's time to adapt

This post provides background and additional resources for my talk on Responsive Web Design in Africa. Last update: May 23, 2013.

I’ve seen a surprising amount of pushback on responsive design within the South African web community recently. The skepticism is mostly based on issues such as low smartphone share and high data costs in Africa, along with assumptions about “the mobile context” and how people supposedly have vastly different needs on mobile phones than they have on their desktops.

So, the purpose of this talk is to summarize the case for Responsive Web Design, and to argue that the reasons against using this approach in Africa don’t hold up. Smartphones and data access are exploding in Africa, so if we want to be Future Friendly, we don’t have a choice. We have to adapt.

The slides for the talk are below, although of course, some context gets lost without the voiceover. There are also embedded gifs and videos that obviously don’t play within Slideshare, so you’ll have to use your imagination on those…

View on Slideshare: Responsive Web Design in Africa - why it’s time to adapt


Resources

I cite the source for each quote, example, and data point on the applicable slide, but I thought it would be helpful to provide a brief list of Responsive Web Design resources here for easy reference.

For those who want to dig a little deeper on the data in Africa, here’s a list of the reports and presentations I found most useful:

Here’s an incomplete list of introductory articles to get you started on responsive design. These articles mainly touch on topics I bring up in the talk, like the reasons for adopting responsive design, performance issues, and RESS:

If you’re looking for responsive patterns, start here:

And here are some ideas for dealing with responsive images:

For more great resources on responsive design, see Jeremy Keith’s extensive list.


The point

My goal with this talk was not to say anything groundbreakingly new about Responsive Web Design. The goal was to urge designers and developers who work in developing regions to take responsive design seriously, and at the very least consider the approach for their next projects.

If you have any questions or comments (or are interested in having me come present this talk somewhere), please get in touch.

Responsive Web Design

[Sponsor] PDFpen 6 from Smile

I’d like to thank PDFpen 6 for sponsoring Elezea’s RSS Feed this week.

If you need to do anything with PDFs, you need PDFpen. Add a signature, make changes, correct a typo, fill out forms, and more. Got a scanned document? PDFpen includes OCR to convert that scan into text that you can search or edit. Want to remove sensitive info such as tax ID numbers from your PDF? Use PDFpen to redact your private data.

The latest version, PDFpen 6, has improved interface and tools. And now you can export your PDFs to Microsoft Word format for sharing or editing. See the new features in action in this video by David Sparks.

Buy PDFpen for $60 in the Mac App Store or directly from Smile. Or buy PDFpenPro for $100 and you’ll get advanced features like form creation tools and document permission settings. Download the free demo!

PDFpen 6

Sponsorship by The Syndicate.

Bitcoin and the growth of "formal-informal" markets

I know very little about Bitcoin, and I’m almost too afraid too dive into the rabbit hole, but I did enjoy Scott Smith’s Bitcoin is just the poster currency for a growing movement of alternative tender. Instead of the usual discussions around its mechanics, Scott focuses on the reasons for the rise in alternative currencies in general, linking it to globalization and the rise of “formal-informal” markets. He also discusses why Bitcoin itself could be doomed already:

“Most of the action I see is around software development—people getting excited by local currency platforms, or virtual currencies,” wrote [Ken Banks, founder of a global initiative to promote economic self-sufficiency Means of Exchange]. “The problem here is that these are generally being run by techies, and we need to lead with the problem we’re trying to solve, not a cool technology. Most of the software being developed is unusable unless you have a degree in computing, or a server that costs about the same as a small car, and is hard to understand.”

You know what’s coming, right? Yep — this applies not just to Bitcoin, but to all product development. If you lead with technology instead of the problem you’re trying to solve, the resulting product will almost always be too complicated. It reminds me of a great line in the USA Today story Berlin airport fiasco an embarrassment for Germans:

Here, again, technology’s getting in the way: It’s so advanced that technicians can’t figure out what’s wrong with it.

So advanced that no one can figure out what’s wrong with it… Perhaps that’s the problem with Bitcoin, too?

Responsive design vs. Separate mobile sites

Chris Ferdinandi wrote a good summary of the responsive site vs. separate mobile site debate in Content Parity on the Web:

The gentleman I was chatting with mentioned that for mobile users, he intended to share about 50 percent less content and reduce the steps in their checkout process to make it more efficient. I think that’s a great idea, but I don’t think it should be limited to the mobile site.

If 50 percent less information is the right amount of information people need to complete their tasks, then you should only provide that 50 percent on all devices. And if visitors on laptops could use that additional information, why wouldn’t someone on a smaller screen want access to it, too?

Whenever I chat to people about Responsive Web Design, there are always arguments about how users want different information on mobile devices than on desktops. This usually plays into the myth of mobile context, but in some cases, there are legitimately different use cases. In those cases I press on to argue that separate use cases are not proof that you need a separate mobile site, but proof that your Information Architecture needs some additional work to make the right information easily accessible regardless of the device being used.

But we’re still figuring this out, of course — no one has all the answers. Just reading through some of Luke Wroblewski’s notes from BD Conf got my head spinning again. So anyway, if you’re in Cape Town next Thursday and want to argue with me about this stuff in person, I’m doing a talk called Responsive Web Design in Africa — Why it’s time to adapt at the next SPIN gathering. It should be fun.

[Sponsor] Instatim — a social network for close friends and family

Thanks very much to Instatim for sponsoring Elezea’s RSS Feed this week.

Instatim is a more personal social network that helps you stay in touch with your closest friends, family and co-workers. Engineered for privacy, Instatim is unlike other social networks because we do not store information about our users’ past activities and locations. Your status is shared securely and only to people you have chosen.

Here’s what you can do with Instatim:

  • Status Updates: Keep in touch by posting status updates about what you’re doing (walking the dog, meeting a client, etc.) and reading your friends’ statuses.
  • Expiration Dates: Set an expiration for your status so your family knows how long you will be engaged in the activity.
  • Groups: Sort contacts into different groups. Share statuses with specific groups to keep the right people in the right loop.
  • Location: You can choose to include your location with your status so your friends and family know your whereabouts.

Download Instatim for free in the App Store.

Instatim

Sponsorship by The Syndicate.

Facebook is not a website, it's a data set

One of the most interesting analyses I’ve read about Facebook’s ad business and the future of the company is Kurt Eichenwald’s Facebook Leans In. This Marc Andreessen quote stood out immediately as core to a proper understanding of how Facebook works:

None of the people close to Mark and the company think of Facebook as a Web site. They think of it as a data set, a feedback loop.

Kurt does a stellar job of piecing together information from different sources to tell a compelling story:

The Facebook of old—well, of a year ago—is almost irrelevant to the company that exists today, which not only is set to change the world of social networking, but could herald the biggest transformation in American advertising since the advent of television.

That is my conclusion from months of interviews with Facebook ad clients, investors, the company’s senior management and other key executives, as well as reviews of reams of data, including confidential reports. What emerges is a portrait of a widely misunderstood company that has quietly been pioneering a marketing business model unlike any other in Silicon Valley—or, for that matter, Madison Avenue.

It’s a long article, but if you’re at all interested in how Facebook is redefining the ad business, it’s a must-read.

(link via @kbaxter)