From Older Entrepreneurs to the Do’s and Don’ts of Effective Web Design

Every week I read thousands of blog posts. Here, for your weekend enjoyment, are some highlights from my recent reading, for you.

01_old-entrepreneur

On Starting Up…

http://www.avc.com/a_vc/2009/10/swinging-for-the-fences.html
Finding success with the other kind of entrepreneur, older and serial.

 
 

On Design & Product Experience…

http://webdesignledger.com/tips/20-dos-and-donts-of-effective-web-design
Effective web design comes about by paying heed to specific do’s and don’ts. A conversation, with examples, exploring many of them.

02_design-do-dont
03_content-modularity

On Modular Innovation…

http://blog.programmableweb.com/2009/10/21/content-modularity-more-than-just-data-normalization/
On the importance of content modularity to Modular Innovation.

 

Have a great weekend!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!
About these ads

jQuery Plugin: It’s CuteTime!

jquery-logo-256 02_facebook-cutetime Many online social products, and more continue to, avoid a formal timestamp format…

2009-10-10 23:14:17 and Thu, October 29, 2004 12:14:19 PM

… opting for more user friendly, “warm and fuzzy,” human-readable styles…

9 days ago and 5 years ago.

As a result, and also in my quest to always help provide my clients free, cheap and easy to use tools, I have been on the lookout for a jQuery plugin that would provide the ability to easily…01_digg-cutetime

  • convert timestamps to ‘cuter’ language-styled forms (e.g. yesterday, 2 hours ago, last year, in the future!),
  • customize the time scales and output formatting, and
  • dynamically update the displayed CuteTime(s) upon request and/or automatically.

While there are other similar tools out there in JavaScript, PHP, and, I am sure, many other languages, none adequately met my goals. Therefore, I created the jQuery CuteTime plugin.

Usage

CuteTime is a customizable jQuery plugin (jQuery.cuteTime) that automatically converts timestamps to formats much cuter. Also, it has the ability to dynamically re-update and/or automatically update timestamps on a controlled interval.

As a Function

If used as a function, a string containing a cuteTime version of the provided timestamp is returned.

$(document).ready(function () {
	// timestamp MUST be a valid Date().parse 'able' format
	$.cuteTime('2009/10/12 22:11:19');
});
<html>
	<body>
		<div class='predetermined'></div>
	</body>
</html>


As a Method

If used via Selector, CuteTime replaces the text of the provided object with a cuteTime.

$(document).ready(function () {
	$('.timestamp').cuteTime();
});
<html>
	<body>
		<div class="timestamp">
			2009/10/12 22:11:19
		</div>
		<div class="timestamp">
			2008/11/01 07:11:00
		</div>
		<div class="timestamp">
			2018/11/01 07:11:00
		</div>
		<div class="timestamp"></div>
		<div class="timestamp" cutetime="1980/10/12 22:11:19">
			2009/10/12 22:11:19
		</div>
		<div class="timestamp" cutetime="asd">
			10/12/2009 22:11:19
		</div>
		<div class="timestamp" cutetime="asd">
			aoisd
		</div>
		<div class="timestamp" cutetime="asd"></div>
	</body>
</html>

When initialized, the cuteTime() call either updates or assigns the ‘cutetime’ attribute to the provided objects. Method implementation supports chaining, returning the jQuery object.

e.g. <div class=’timestamp’ cutetime=’2009 10 12 22:11:19′>2009 10 12 22:11:19</div>

If the cutetime attribute already exists within the provided object, then the text within the object is ignored in the cutification process. If the cutetime attribute does not exist or an invalid one is provided, then a valid cutetime attribute is assigned to the object.

If the cutetime attribute is missing, then it is calculated from the text of the provided object.

If neither cutetime attribute nor valid object text exist, then the timestamp is assumed to be ‘now’.

When using CuteTime in the form…

<br />
$(document).ready(function () {
	remember_the_cuteness = $('.timestamp').cuteTime();
});

… the following methods can be used …

// stops all automatic updates of refresh-enabled timestamps
remember_the_cuteness.stop_cuteness();

// (re)starts the automatic updating of timestamps
// REMINDER: make sure refresh is set to > 0
remember_the_cuteness.start_cuteness();

// updates timestamps of the provided objects
remember_the_cuteness.update_cuteness();

Settings

By default, automatic updating is disabled and the following CuteTimes can be displayed…

the future!
just now
a few seconds ago
a minute ago
x minutes ago
an hour ago
x hours ago
yesterday
x days ago
last month
x months ago
last year
x years ago

To change these settings, they can either be accessed directly…

$.fn.cuteTime.settings.refresh = 10000;

… or at the time of initialization …

my_cutetime = $('.timestamp_move').cuteTime({ refresh: 60000*10 });

The default settings data structure is…

$.fn.cuteTime.settings = {
	refresh: -1,			// time in milliseconds before next refresh of page data; -1 == no refresh
	time_ranges: [
		{bound: NEG_INF,	// IMPORANT: bounds MUST be in ascending order, from negative infinity to positive infinity
			cuteness: 'the future!',			unit_size: 0},
		{bound: 0,
			cuteness: 'just now',				unit_size: 0},
		{bound: 20 * 1000,
			cuteness: 'a few seconds ago',		unit_size: 0},
		{bound: 60 * 1000,
			cuteness: 'a minute ago',			unit_size: 0},
		{bound: 60 * 1000 * 2,
			cuteness: ' minutes ago',			unit_size: 60 * 1000},
		{bound: 60 * 1000 * 60,
			cuteness: 'an hour ago',			unit_size: 0},
		{bound: 60 * 1000 * 60 * 2,
			cuteness: ' hours ago',				unit_size: 60 * 1000 * 60},
		{bound: 60 * 1000 * 60 * 24,
			cuteness: 'yesterday',				unit_size: 0},
		{bound: 60 * 1000 * 60 * 24 * 2,
			cuteness: ' days ago',				unit_size: 60 * 1000 * 60 * 24},
		{bound: 60 * 1000 * 60 * 24 * 30,
			cuteness: 'last month',				unit_size: 0},
		{bound: 60 * 1000 * 60 * 24 * 30 * 2,
			cuteness: ' months ago',			unit_size: 60 * 1000 * 60 * 24 * 30},
		{bound: 60 * 1000 * 60 * 24 * 30 * 12,
			cuteness: 'last year',				unit_size: 0},
		{bound: 60 * 1000 * 60 * 24 * 30 * 12 * 2,
			cuteness: ' years ago',				unit_size: 60 * 1000 * 60 * 24 * 30 * 12},
		{bound: POS_INF,
			cuteness: 'a blinkle ago',			unit_size: 0}
	]
};

The parameters are defined (and all can be overridden) thus…

  • refresh
    • time in milliseconds before next refresh of page data;
    • a value of -1 disables refreshing
  • time_ranges
    • the array of bound_structures that delineate the cute descriptions associated with time_ranges
    • time_range’s boundary structures consist of the following variables…
  • time_range[x].bound
    • the value is an integer representing the time difference between the provided timestamp and now
    • the lower inclusive bound, or starting point, for using the ‘cuteness’ string that describes the current timestamp
    • the exclusive upper bound is defined by the next boundary structure definition in the time_ranges array [current boundary + 1]
  • time_range[x].cuteness
    • string to use in place of the current timestamp (e.g. ‘yesterday’)
  • time_range[x].unit_size
    • the integer divisor in milliseconds to apply to the calculated time difference
    • if unit_size > 0 then a number value is prepended to the cuteness string as calculated by time_difference / unit_size (e.g. 4 hours ago)
    • if unit_size = 0, then no number is prepended to the cuteness string (e.g. an hour ago)

BTW

Make sure you use timestamps that are fully recognized by the JavaScript Date object’s Parse method in all the IE and FF browser versions you want to support. Otherwise, prepare for a headache. ;-)

Get It

You can download CuteTime, dual licensed under GPL and MIT, from…

jQuery Repository
http://plugins.jquery.com/project/CuteTime

Git
Public Clone URL: git://github.com/theproductguy/CuteTime.git
GitHub: http://github.com/theproductguy/CuteTime

Zip
jQuery.cuteTime_source-bundle_1.0_20091019.zip

Demo

http://theproductguy.com/cutetime/cutetime.demo.html

Status updates can be found here, jQuery CuteTime.
If you find this useful, or have any questions, ideas, or issues, leave a comment.

Enjoy!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!

From Another Facebook Facelift to IBM’s Bridging of Worlds through Modular Innovation

Every week I read thousands of blog posts. Here, for your weekend enjoyment, are some highlights from my recent reading, for you.

01_five

On Starting Up…

http://www.undertheradarblog.com/blog/the-series-a-term-sheet-5-terms-founders-should-focus-on/
Series A fundraising and the 5 terms every founder should know.

 
 

On Design & Product Experience…

http://www.fubiz.net/2009/10/19/facebook-facelift/
Facebook gets another facelift.

03_fb-facelift
02_ibm

On Modular Innovation…

http://www.readwriteweb.com/archives/humans_as_sensors.php
IBM’s bridging of online and offline worlds through Modular Innovation and human sensors.

 

Have a great weekend!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!

Another Gmail Problem – Inescapable IO

gmail_logo_stylized_thumb3534This is part 4 of a short story of personal exploration and development by one new to the daily employment of Gmail, long resisted, long desired, and eventually brought to conversion by an Android.

Part 4: To Resist

Recently our journey began. From the humble origins of Outlook to the portable synchronicity of the Windows Mobile platform, I did travel, did evolve, as needs, desires, and demands of communication and productivity so evolved and changed. Through the darkness of masked potential so emerged new and exciting opportunities. But, to fully grasp this fortune, these new degrees of productivity, it is important to pause, take measure of, and understand the crux at the heart at the core of the resistance to Gmail.

I am often asked, more so in the days since my recent conversion to Gmail, what is was, specifically, precisely, that caused me to build up such a strong aversion to a product such as this. The constitution of my answer is thus…

Inescapable IO (Information Overload)

00_gmail_discussion-thread Almost on par with the deficiency of means of acclimation available to (potential) Gmail converts, is the onerously persistent burden of IO — Information Overload. From the beginning of Gmail there have always been discussions, a construct of threaded conversations, automagically grouped, combined, amalgamated into lists.

00_gmail-all Lists, and of lists, bombarding, overwhelming with line after line after line of content with no simple, no familiar way to dig out. A monotony of information, endless in its flattened constancy. Of course, this is a monotony not universal to this method of interchange, for where others have embraced the grouped order hills (sub-folders) comingled with sowed valleys (sorted) and ranges (folders), Gmail plows this all down in lieu of a different order. By these flattened plains, stretching outward, there is no way to easily zoom into what is important, have a sense of past, localized exchanges. With the horizon the only visible bound, without knowing exactly of that for which you seek, it is easy to become lost, no characteristics, no landmarks to point the way, no approach to lead the way between the here and there.

However, in this new order, for as far as the eye can see, there exist few instruments to either approach or approximate the supposedly archaic structures of the prior lands (Outlook, Exchange, Windows Mobile). Digging is limited to the most simplest of shovels, requiring a precision of intent previously unnecessary. For buried deep within a list, unsortable, unorganizable, may be that sought after thing, yet only revealed to the skilled, the lucky, in finding the magic word, the keyword.

02_gmail_search

And then there are those younger conversations, active, full of life, in the here and now. Conversations woven into threads, subject-locked, compressed together, layer upon layer, each exchange compounding each further layer another more, until at last, with the grounds of this conversation deeply rooted, only then, within this vastly growing mound does one realize that there may be more than one or two who have suffered the fate of being buried alive, messages unread, deep within the endlessly scrolling, organizably deficient, active discussion threads; where many an unread message have before, too been lost.

gmail-thunderbird-screenshot Sure, such structures have their merits, especially in contrast to those ‘archaic’ (Outlook, Exchange, etc.). But with no means by which to avoid or mitigate the suffocating enclosures of the hierarchically challenged experience, with few approximating tools, with the IMAP equivalents merely presenting additional schmutz to the pile that was already heaping layer upon layer of Information Overload, with minimal ability to shift around, to lessen the burden, the paths toward maintaining the productivity and efficiencies of time past can easily be obscured.

The Resistance

But, what of the other reasons for my resistance, which managed to be sustained from the early days of the private Gmail beta to the most recent of but few weeks passed? For surely there must be more to such a stalwart position as has been held by me, and I am sure many others still, for, for them, the resistance most definitely continues. And, indeed there are. In addition to…

Exiguous Encouragement, and
Inescapable IO (Information Overload)

… there too are the staunch galvanizers of resistance …

Suffersome Slowness, and
Tiny Things.

The Next

And, these propellants of reluctance, delayers of adoption, the fundamental causes of my resistance to what would eventually be overshadowed and forced aside, through the coercion of an Android to my conversion to the ways of Gmail, will, my friends, have to wait until next week.

Subscribe now (click here) to make sure you don’t miss any part of this series exploring the eventual adoption of Gmail in one’s daily life, by one once thoroughly addicted to, dependent on, the primarily client-based solution of Microsoft’s Outlook,

what brought about this conversion, (1) (2)
why it took so long, and (3) (4) (5) (6) (7)
what should be done to encourage greater Gmail adoption. (8) (9)

Enjoy & Tweet!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!

From the Search for a Co-Founder to the Design Trends of iPhone Apps

Every week I read thousands of blog posts. Here, for your weekend enjoyment, are some highlights from my recent reading, for you.

01_cofounder

On Starting Up…

http://www.techcrunch.com/2009/10/11/finding-your-co-founders/
To find a co-founder.

 
 

On Design & Product Experience…

http://www.smashingmagazine.com/2009/10/09/iphone-app-design-trends/
A look at the design trends of iPhone applications.

02_iphone-trends
03_jaiku

On Modular Innovation…

http://www.techcrunch.com/2009/10/12/aiming-to-make-meaning-jaiku-co-founder-leaves-google/
Jaiku co-founder leaving Google to ‘make meaning’ in Modular Innovation?

 

Have a great weekend!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!

The Gmail Problem – Encouragement

gmail_logo_stylized_thumb35[3]This is part 3 of a short story of personal exploration and development by one new to the daily employment of Gmail, long resisted, long desired, and eventually brought to conversion by an Android.

Part 3: To Resist

Recently our journey began. From the humble origins of Outlook to the portable synchronicity of the Windows Mobile platform, I did travel, did evolve, as needs, desires, and demands of communication and productivity so evolved and changed. Through the darkness of masked potential so emerged new and exciting opportunities. But, to fully grasp this fortune, these new degrees of productivity, it is important to pause, take measure of, and understand the crux at the heart at the core of the resistance to Gmail.

I am often asked, more so in the days since my recent conversion to Gmail, what is was, specifically, precisely, that caused me to build up such a strong aversion to a product such as this. The constitution of my answer is thus…

Exiguous Encouragement

00_gmail-all

To be unwelcomed into foreign arms was foremost the chief reason for my resistance. Over the years I have proven myself adaptive, willing and eager to try and learn new skills, especially of those that possess the potential to further optimize my relationships and time spent thereupon. This cause, perhaps the best embodiment of my duality of desires, the eagerness to embrace, coupled with the strenuous resistance to adopt, too had solutions’ twain — to either or both acclimate or assist.

To acclimate, the more desirous of the paths would have been to support an easing shift, a reduction of the jagged peaks on this most mountainous path to the gentle current of reorganized communication. To teach one, myself, how to swim this new stroke in this new lane, would be to show me, teach me, facilitate my gradual, incremental evolution. Providing an environment wholly novel and new, with no path to acclimation nor encouragement in transition, a total dunking in the deep end, from user interface to other parallels of familiarity that could bring me forth, predicates the alternative, of the lowest common denominator, to assist.

01_google-apps-sync To assist, the tools of self determination would enable the toe dipping into the Gmail pool. To be able to straddle, with one foot in each, the choices, both presenting their own unique experiences, both available to cater to my liquid needs, would have, in an unforceful fashion empowered me to, myself, make the decision as to when I felt I was fully ready to jump into this new pool. Recently, and for far longer at 03_google-syncthe exclusive enterprise level, tools of synchronization do exist, but fall/fell short in timing and implementation — from seamlessness to bidirectionality; capabilities becoming better addressed and more widely available since my full on dive in.

 

The Resistance

But, what of the other reasons for my resistance, which managed to be sustained from the early days of the private Gmail beta to the most recent of but few weeks passed? For surely there must be more to such a stalwart position as has been held by me, and I am sure many others still, for, for them, the resistance most definitely continues. And, indeed there are. In addition to…

Exiguous Encouragement

… there too are the staunch galvanizers of resistance …

Inescapable IO (Information Overload),
Suffersome Slowness, and
Tiny Things.

The Next

And, these propellants of reluctance, delayers of adoption, the fundamental causes of my resistance to what would eventually be overshadowed and forced aside, through the coercion of an Android to my conversion to the ways of Gmail, will, my friends, have to wait until next week.

Subscribe now (click here) to make sure you don’t miss any part of this series exploring the eventual adoption of Gmail in one’s daily life, by one once thoroughly addicted to, dependent on, the primarily client-based solution of Microsoft’s Outlook,

what brought about this conversion, (1) (2)
why it took so long, and (3) (4) (5) (6) (7)
what should be done to encourage greater Gmail adoption. (8) (9)

Enjoy & Tweet!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!

From the Importance of Handling Nothingness to Better Expression through Type

Every week I read thousands of blog posts. Here, for your weekend enjoyment, are some highlights from my recent reading, for you.

01_404

On Starting Up…

http://webanalysis.blogspot.com/2009/10/7-ways-of-handling-404-error-messages.html
Sometimes more important than what you company is offering is what you offer when there is nothing to be found at all.

 
 

On Design & Product Experience…

http://www.myinkblog.com/3-powerful-ways-to-make-typography-talk-on-your-website/
A key component of a web product’s overall experience is Typography. A great set of tips on how to better express through ‘type.’

02_typography
03_pachube

On Modular Innovation…

http://www.readwriteweb.com/archives/applications_from_the_internet_of_things_pachube.php
Pachube’s Modular Innovation efforts in enabling a more interconnected, sharable online world.

 

Have a great weekend!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!

The Product Group, Cycles and Waves: Thanks for Coming!

theproductgroup_logo_200909
balsamiq_logo2

A big thank you to everyone who made it to the inaugural meet-up of The Product Group, as well as to our sponsor, Balsamiq Studios! We all had a blast discussing Product People-oriented topics and enjoying Wonderful food.

Group_Pic_1_20091001

Over the 2 hours we discussed…

Product Development Cycle: tips, challenges, advice

Google Wave: the strategy behind it, Google, and online collaboration

Product Focus & Organization: tips for keeping your product on track and how to avoid the problems of the ‘heads down’ dilemma

The Product Group meet-ups are an opportunity for Product People (managers, strategies, marketers, etc.) to come together to meet, interact, and network in a roundtable setting. It’s awesome to meet fellow Product People in a laid-back, conversational gathering like this one and I am looking forward to seeing everyone, new and familiar, at our next meet-up …

Thursday, November 5th @ 7PM
@ Wonderful @ 172 8th Avenue (bet. 18th and 19th St)
NYC

If you would like to attend our next meet-up, RSVP today or visit our group webpage at…

http://meetup.com/TheProductGroup

Enjoy!

Jeremy Horn
The Product Guy

P.S. If you or an organization you represent would be interested in sponsoring an upcoming gathering of The Product Group please contact me.

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!

Venit Vidi — On the Path to Gmail, I met an Android (2)

gmail_logo_stylized_thumb3This is part 2 of a short story of personal exploration and development by one new to the daily employment of Gmail, long resisted, long desired, and eventually brought to conversion by an Android.

Part 2: Fall and Android

model-t Last week our journey began. From the humble origins of Outlook to the portable synchronicity of the Windows Mobile platform, I did travel, did evolve, as needs, desires, and demands of communication and productivity so evolved and changed. Happy so this journey was, but to me unknown was the approaching end of this long traveled path, a fork in the road, nay, a change in elevation, a transformation of transportation on par with from horse to Model-T, would be a more accurate rendition of the next.

Often there is a little bit of darkness before the coming light. And, here too, this journey, is no different.

The Darkness

A darkness enveloped my already struggling Windows Mobile device; a device that had seen me through many a harrowing experience. Its age beginning to take a toll, it’s memory failing, no longer able to recall a phone number, install a new application, or for that matter, uninstall another. Its joints holding true, but clearly, obviously, succumbing to one too many a fall. It was clearly time for us to part ways, to let go, not linger over memories of good times past, proud unboxings of self and of parts, and shiny new suits of UI. But, to move on, it had become abundantly clear in my device’s last days that, I would be, should be moving on to technologies, new, more powerful, more evolved, more ready to receive me and my data, grow with me and my data; things that my decrepit device, as well as its new born decedents, was no longer capable.

Years of no true improvements to email, calendar, to do’s — I evolved, and it did not; I improved and it did not.

broken-heart-main_Full Such things can strain even the best of relationships, and I do not claim to be special or unique in my such relationship, for comfort had set in, years upon years of comfort, cohabitation with one organized like I thought, worked like I wanted (at least for the most part), whose flaws I had come to see less as such and more as mere traits making for the spice of and helping shape the unique character of this relationship. In retrospect, my Windows Mobile device always had seemed a hair behind the capacities of what I at least recalled of my old Palm PDA.

It Came

But to move on, to look elsewhere, brought forth its own set of challenges. To what device, to what platform, by what means would I find fitting in my desires to continue my ever improving evolution of efficient information, communication and its portability?

Since I had started my journey with Windows Mobile, many viable alternatives, worthy of my consideration, had come onto the scene, most notably, Apple’s iPhone, Palm’s Pre, and Google’s Android.

Iphone 3Gs I flirted, I courted, got to know, built relationships, understandings, with each and every of my new future partners. Despite iPhone’s allure, its sleek and sexy curves, in the end, I found its elitist tendencies (for it would only work with AT&T) and controlling ways (of the developer community) to be too much, a turn off, that pushed me away, and towards the Palm Pre. palm-pre From everything I heard, up to and until I met Pre, it was a friendly device, open to new things and ways of thinking, adaptable, flexible, familiar, everything I could possibly want in another. But, this relationship rapidly followed the fate of my prior encounter. While not immediately evident, Pre eventually revealed similar controlling ways. Those tendencies coupled with the occasional sluggish behavior of its UI experience, and stunted keyboard, and desires for more exclusive relationships (Sprint, non-GSM), lead to a breakup that occurred as quickly as the initial romance was strong.

Had I made a mistake in abandoning one who I had come to know, implicitly understanding its quirks and eccentricities? Had I abandoned the one who had loyally, consistently been with me for so long? On this point I stumbled, looked back, reconsidered. Yet, reluctantly, decided to one last time, give one new look, at one final thing.

My initial impressions of every Android I had heretofore seen, were ones of bewilderment, if not repulsion, from its goofy chin, to odd UI. But, time was running out, a decision was needed, to what new device, new platform, new paradigm, would I be shifting was of utmost importance in rapid determination. In the end, the openness, flexibility, kindness to strangers (developers), its constant, open, and frequent development, improvement, and evolution, sealed the deal.

android-wallpaper5_1024x768

While I was not 100% committed to this relationship at first, I jumped in, two feet; for it was the best of the choices before me at the time, and I would have to be saying ‘goodbye’ to my old friend very soon.

The Conversion

Part of what helped me make this life altering transition was the knowledge that my device, my Android, unlike many that had come before it, would also have abilities to bridge new and old, Gmail and Exchange.

Immediately I setup Exchange, and inputted my Gmail credentials. For, as at that time, I presumed I could continue using Exchange as my primary method of organization with Gmail (and Calendar, ..), my backup.

I was sorely mistaken. The concept of folders on my, now retired, Windows Mobile device, while mostly unusable, did exist, and could be navigated. Now, HTC’s deflating interpretation and subsequent implementation led to an experience quite flat. htc-exchange-flat And, by flat, I mean both emotionally and literally — the hierarchical folder structure, common to the ways of Exchange, Outlook, and Windows Mobile were completely flattened, with all hierarchical footprints and guidance squashed and eliminated.

So, with little alternative available, by initial choice, but then by extreme force, I was converted to Gmail by an Android. Oh yes, at first I resisted, frustrated by the lack of control of my fate, my next steps. I was bound to this path, struggled to look for a logical way back, a way out, to return to the familiar, the comfortable, hierarchically organized world from whence I came. I resented what I saw as trickery, or even, in my darkest moments, lies about what this device was going to be able to do for me.

But, in the end, I converted. Yes, at first kicking and screaming, frustrated and yelling, bewildered and confused, however, in the end, happier, more productive, more efficient, more connected, more modular than ever before in this, this journey of mine.

My email in sync,
my calendar, too.
New apps installed,
enabled yet more productivity to accrue.

The Next

First converted to a fan of Android, the platform, then converted to a fan of Gmail, too. I resisted the Android, and succumbed. I, for much longer, both longed for and resisted the conversion to Gmail. But, that, my friends, that part of this short story, I will save for next week.

Subscribe now (click here) to make sure you don’t miss any part of this series exploring the eventual adoption of Gmail in one’s daily life, by one once thoroughly addicted to, dependent on, the primarily client-based solution of Microsoft’s Outlook,

what brought about this conversion, (1) (2)
why it took so long, and (3) (4) (5) (6) (7)
what should be done to encourage greater Gmail adoption. (8) (9)

Enjoy & Tweet!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!

From Facebook’s Modular Innovation Initiative to the Evolution of an Interface

Every week I read thousands of blog posts. Here, for your weekend enjoyment, are some highlights from my recent reading, for you.

01_pm-advice

On Starting Up…

http://crankypm.com/2009/09/10-cranky-product-manager-learned-product-management/
Some good advice for managing your products and the people around them.

 
 

On Design & Product Experience…

http://www.everydayux.com/2009/09/28/design-in-the-wild-convert-and-the-evolution-of-a-user-interface/
The evolution of an interface.

02_convert-ui
03_andreessen

On Modular Innovation…

http://www.nytimes.com/2009/08/14/technology/internet/14browser.html?th&emc=th
Facebook heating it up with a new Modular Innovation initiative.

 

Have a great weekend!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!