Blog | Silex Technologies, India

The rantings of a serial entrepreneur as he wins, loses, and doesn’t pull any punches in describing both..

Pix of the week

cartoon-1

Filed under: Pix of the week , , , , , ,

Design / Architect Carefully for Mobile Sites

Mobile-web-site

Adaptive Path, an experience strategy, user research and design firm recently announced the completion of their Mobile Literacy project. They studied mobile device usage in rural Gujarat, India.

As the lead Experience Architect for Chrysler International, I’m anxious to learn the full findings of their study. One tidbit of information agrees with what we learned researching our International mobile users. (Check out the Jeep South Africa site on your phone — or shrink your PC browser.)

In many parts of the world, low cost mobile phones are more often used than PCs to access the Web. In fact, many international users do not own a PC, so they access the web exclusively from their mobile devices.

So what does this mean for those of us trying to reach these audiences? Here are three crucial tips to consider when planning:

1.
First and foremost, do not ignore the need to create an exclusive mobile website. While many users will attempt to access your sites from their mobile devices, this will only lead to frustration. It’s very likely that parts of the architecture, page weight, and technology will not work in a mobile web browser.

2. Take the time to consider your navigation and architecture. Top nav, side nav or however you’ve structured your navigation does not translate to the mobile architecture. Instead, you’ll need to create a nested architecture and rely heavily on breadcrumb trail navigation.

3. Be ready to pare down your content. Your mobile website shouldn’t be simply a modification of your existing site. Leave out information that isn’t relevant to a user on the move. It’s not a likely that a mobile user will browse for extended periods of time, so it’s important that you surface the information most relevant to them.

Filed under: Thought of the day , , , , , , , , , , ,

Packaging Design: If Harry Potter Did!!

Check out this unboxing video for the Samsung WB1000. Ok, it’s a spoof but a very clever one. I was fooled at first and I don’t think I was the only one judging by the comments.

The interesting thing is that the video is posted in two places. On Samsung’s Youtube page, as well as a regular user edanhush184, who seems to be getting more views than Samsung’s page.

And what exactly is “unboxing”? One of the most celebrated geek rituals…

“It begins with a rush right from the moment of purchase, whether online or off, to the foreplay of opening the package, examining its contents, and ends with the exhilarating finish of turning on and using your tech toy… Think Lolcats riding rainbow rollercoasters; the sensation in the pit of your stomach…that unforgettable.” Jank (nixiepixel.com)

Filed under: Thought of the day , , , , , , , , ,

Your customers may not know what your product is – and they may not care

This video by Google illustrates several issues that have been plaguing product and brand managers, UxDs (user-experience designers) and IAs (information architects) and most obviously, the general public. Google asks “What is a browser,” only to find that less than 8% of those polled have an understanding of the term. (It is, by the way, “a software application for retrieving, presenting, and traversing information resources on the World Wide Web” – Wikipedia; e.g. Mozilla Firefox or Microsoft’s Internet Explorer (The big blue ‘E’))

For Branders
For those of us concerned with brand definition, the example is clear: Google checks to see if people understand how Chrome is better even have a basic understanding of the term “browser,” and find that the confusion has hardly cleared up over the past 15 years, since graphical browser use became widespread in the mid-’90s. Back then, users thought they “used Yahoo!” to surf the information superhighway, and as we see here, they still believe the same.

For Google Chrome achieve any penetration in this market, the big G needs to focus on not only defining and demonstrating Chrome’s unique value, but also educating the public on the very basic concepts of “browsing,” and “applications.” This is no small task, as Firefox has long been fighting this battle and making slow gains against the IE giant, mostly through word-of-mouth from passionate advocates, again illustrated in the Google video. (I, personally, have done this on many occasions, wiping IE from friends’ and families’ hard drives in a Firefox coup.)

For IAers
For those of us concerned with interface design, the interviews illustrate the need for simplicity. This video may make you consider an edit or two if your web site copy includes the call-to-action “Download to your browser,” or similar industry-insider phrases. On a more macro level, the interviews highlight the importance of maintaining a holistic view of the web experience.

If your users don’t really understand what a browser is, do they know when they are on your web site, or is your vanity URL confusing this; perhaps they’re on an “unofficial” site created by a passionate fan?

If your users don’t really understand what a browser is, do they think they have to come through Google or Yahoo! to reach your site? Do you show up (positively) there?

If your users don’t really understand what a browser is, are they savvy enough to find their way through your site; are they stymied by nomenclature that is cloaked in your brand’s jargon or Internet industry jargon?

I don’t care what a browser is.

Ultimately, this video illustrates the fact that people don’t really care how they get what they want online, just that they get it. The best thing your brand, product or digital experience can do is make it easy and understandable for your customers.

So for product and brand managers; UxDs and IAs, the questions become, does your market know what your brand promises? Do they know what your product does? Do they know what that button does or where that link goes?

Or, does your market make assumptions about your product, lumping it in with a lesser offering, mistaking it for your competition, or for a completely different idea?

If so, you have a lot of work to do. Maybe it’s time to hit the pavement and get some real insight from real customers.

Filed under: Thought of the day , , , , , , , ,

Yahoo Mail Is Stepping It Up

yahoo-mail-june-2009

When new CEO Carol Bartz took the reign at Yahoo she promised to shake things up a bit and she held true to her promise. For the past several month, Yahoo has improved their UI and discontinued less popular services like the ‘briefcase”. Last week they launched access to “applications” right from your Yahoo inbox. I love the direction they are going. I have been using Yahoo Mail for as long as I can think and must admit I never got used to the Gmail interface. I might be a bit old fashioned that way.
 
Y! Mail also launched the “Connections Bar” a few weeks ago, but it seems to be removed from the interface now. I believe it is an attempt to integrate popular social networking features into your mailbox. The only issue is that you have to invite people to become connections and then it just seems like a filter for your inbox. Hopefully they have some more ideas to make this feature more valuable.
 
I like that they are making an effort to improve their services. I did, however, notice that Yahoo has a tendency to launch buggy services. Maybe they put more emphasis on speed to market and less on quality. I did just get a serious browser error when I tried to active my Flickr account in the application below. Generally I am a firm believer in high quality, because to me, first impressions can make or break a deal. Plus some folks may never go back and try it a second time if it hasn’t worked the first time. Well…I cut the folks at Yahoo some slack because I like my Y! Mail.

How do you feel about companies being too quick to launch something that still has a few kinks?

Filed under: Thought of the day , , ,

Murphy’s Computers Laws

current

Murphy’s Computers (IT & Software) Laws

  • Any given program, when running, is obsolete.
  • Any given program costs more and takes longer each time it is run.
  • If a program is useful, it will have to be changed.
  • If a program is useless, it will have to be documented.
  • Any given program will expand to fill all the available memory.
  • The value of a program is inversely proportional to the weight of its output.
  • Program complexity grows until it exceeds the capability of the programmer who must maintain it.
  • Every non trivial program has at least one bug
    Corollary 1 – A sufficient condition for program triviality is that it have no bugs.
    Corollary 2 – At least one bug will be observed after the author leaves the organization.
  • Bugs will appear in one part of a working program when another ‘unrelated’ part is modified.
  • The subtlest bugs cause the greatest damage and problems.
    Corollary – A subtle bug will modify storage thereby masquerading as some other problem.
  • Lulled into Security Law
    A ‘debugged’ program that crashes will wipe out source files on storage devices when there is the least available backup.
  • A hardware failure will cause system software to crash, and the customer engineer will blame the programmer.
  • A system software crash will cause hardware to act strangely and the programmers will blame the customer engineer.
  • Undetectable errors are infinite in variety, in contrast to detectable errors, which by definition are limited.
  • Adding manpower to a late software project makes it later.
  • Make it possible for programmers to write programs in English, and you will find that programmers can not write in English.
  • The documented interfaces between standard software modules will have undocumented quirks.
  • The probability of a hardware failure disappearing is inversely proportional to the distance between the computer and the customer engineer.
  • A working program is one that has only unobserved bugs.
  • No matter how many resources you have, it is never enough.
  • Any cool program always requires more memory than you have.
  • When you finally buy enough memory, you will not have enough disk space.
  • Disks are always full. It is futile to try to get more disk space. Data expands to fill any void.
  • If a program actually fits in memory and has enough disk space, it is guaranteed to crash.
  • If such a program has not crashed yet, it is waiting for a critical moment before it crashes.
  • No matter how good of a deal you get on computer components, the price will always drop immediately after the purchase.
  • All components become obsolete.
  • The speed with which components become obsolete is directly proportional to the price of the component.
  • Software bugs are impossible to detect by anybody except the end user.
  • The maintenance engineer will never have seen a model quite like yours before.
  • It is axiomatic that any spares required will have just been discontinued and will be no longer in stock.
  • Any VDU, from the cheapest to the most expensive, will protect a twenty cent fuse by blowing first.
  • Any manufacturer making his warranties dependent upon the device being earthed will only supply power cabling with two wires.
  • If a circuit requires n components, then there will be only n – 1 components in locally-held stocks.
  • A failure in a device will never appear until it has passed final inspection.
  • Adding manpower to a late software project makes it later.
  • A program generator creates programs that are more buggy than the program generator.
  • All Constants are Variables.
  • Constants aren’t
  • Variables won’t
  • A part dropped from the workbench will roll to a degree of un-reachability proportional to its importance.
  • In a transistor circuit protected by a fuse, the transistor will always blow to protect the fuse.
  • The best way to see your boss is to access the Internet.
    Or…
    No matter how hard you work, the boss will only appear when you access the Internet.
  • The hard drive on your computer will only crash when it contains vital information that has not been backed up.
  • Computers don’t make errors-What they do they do on purpose.
  • If Murphy’s laws are so true then how come I can log onto this site and submi…………
    [connection reset - error message 928 ]
  • Gumption’s Law (?)
    Any problem, no matter how complex, can be found by simple inspection.
    Corollary: A nagging intruder with unsought advice will spot it immediately.
  • Each computer code has five bugs, and tis number does not depend on how many bugs have been already found (it is conservative).
  • Profanity is one language all computer users know.
  • The number of bugs always exceeds the number of lines found in a program.
  • The most ominous words for those using computers:  ”Daddy, what does ‘Now formatting Drive C mean’?”
  • When putting something into memory, always remember where you put it.
    Sent by Paul Pigott
  • Every non-trivial program contains at least one bug.
  • Every non-trivial program can be simplified by at least one line of code.
    The conclusion of the last two laws: Every non trivial program can be simplified to one line of code, and it will contain a bug.
    Sent by Brandon Aiken
  • An expert is someone brought in at the last minute to share the blame.
    Sent by Bassey Essien.
  • Debugging is at least twice as hard as writing the program in the first place.
    So if your code is as clever as you can possibly make it, then by definition you’re not smart enough to debug it.
    Sent by Brian Kernighan
  • Bahaman’s Law:
    for any given software, the moment you manage to master it, a new version appears.
    The new version always manages to change the one feature you need most.
  • Patches – don’t.
  • Most computer errors can be attributed to a similar problem – a screw loose behind the keyboard.
  • Whenever you need a crucial file from the server, the network will be down.
  • Whenever you need a crucial file from your hard drive, your computer will crash.
  • E-mailed tasking will always come just before you log off.
  • A quarantined virus – will be opened.
  • A chain letter – will be sent.  To global.  A dozen times.
  • The chance of a virus infecting your network is directly proportional to the amount of damage it does.
  • The chances of getting off work on time is inversely proportional to how much e-mail the boss leaves for until end of the day.
  • The faster you need a hardcopy, the more people will be using the only office printer.
  • General Fault Errors are the “Check Engine” light of computers. If it can be fixed, chances are it’s not by you.
  • A patch is a piece of software which replaces old bugs with new bugs.
  • The chances of a program doing what it’s supposed to do is inversely proportional to the number of lines of code used to write it.
  • The probability of forgetting your password is directly proportional to the frequency of changing it.
  • No matter how fantastic your latest and greatest PC is, you will be able to buy it for half the price in 12 months.
    The last two laws were sent by Zain
  • The longer it takes to download a program the more likely it won’t run.
  • Failure is not an option, it’s included with the software.
  • A program is good when it’s bug free – which is impossible.
  • If you forget to save you’re work every 5 minutes, it will break down after you’ve been at it for an hour.
  • It’s not a bug, it’s an undocumented feature.
  • The amount of time taken to successfully complete a software project is in direct proportion to the amount of Marketing input.
    Corollary: Marketing should not be located in the same city – much less on the same campus – as Engineering and/or Programming.
  • The only thing worse than an end-user without a clue is an end-user who has a clue – usually the wrong one.
  • According to most Tech Support people, the most common user error message (regardless of Operating System) is ID 10T.
    End-users’ Corollary 1: most application failures occur between the hours of 2 and 4 am on a Sunday night – with a 6 am Monday deadline for the project.
    End-users’ Corollary 2: On the graveyard shift, there’s no Tech Support to hear you scream!
  • Bugs mysteriously appear when you say, “Watch this!”
    corollary: If you call another programmer over to see if he knows what’s wrong the bug disappears.
    The corollary was sent by S. Bussell.
  • The probability of bugs appearing is directly proportional to the number and importance of people watching.
    The last two laws were sent by Bill Smith.
  • An employee rank is in inverse proportion to his use of a computer, and in proportion to its performance.
  • The only program that runs perfectly every time, is a virus
  • If a project is completed on schedule, it wasn’t debugged properly.
  • Non Crash Operating System aren’t.
  • The worst bugs in your program will show up only during the final review.
  • The people who say that computers are simple to use are the same people who tell you how to build a watch when you ask what time it is.
  • Philington’s First Law
    If it works, it’s production. If it doesn’t, it’s a test.
  • Philington’s Second Law
    Real programmers don’t comment their code. If it was hard to write, it should be hard to understand.
  • Format C: fixes all
  • Law of Computer Generated Aerodynamics
    Computers suck.
  • Law of Recycling
    A computer that has been on the market for 6 weeks is still usable as a boat anchor.
  • Law of Anti-security
    The best way past a pesky security feature is a 13-year-old.
  • Law of Acceleration
    A computer that has surpassed its user’s frustration capacity (FC) will accelerate downwards at 9.8 meters per second squared.
  • Computers let you waste time efficiently
  • Make a system even a moron can use and a moron will use it.
  • Make one that requires training or intelligence and only a moron will use it, but there will be more help desk calls.
    Sent by S. Bussell
  • The likelihood of problems occurring is inversely proportional to the amount of time remaining before the deadline.
  • You will always discover errors in your work after you have printed/submitted it.
    The last two laws were sent by Niels Hageman
  • 90% of a programmer errors come from data from other programmers.
  • ‘Illegal Error’ messages only happen when you forget to save your work
  • If you make the letters in your Word document bigger and then you print it out, you’ll have everything on the first page and only one line on the second.
  • the OEM did not actually manufacture the part you need to replace
  • By the time you learn your new computer you’ll need a new one.
  • After a software is released, the first bug found will be by a person who normally does not use that portion of the program but was wondering why he can’t do something he normally would not do.
  • When the Downloading Window says “99%complete”, there will be a fluctuation in the voltage and you’ll have to start all over again.
  • Millions of people believe they are animals, but I have yet to meet one that believe in Windows’ stability. Even human stupidity has limits ;-)
  • The troubleshooting guide contains the answer to every problem except yours.
  • Plugins Law
    Whenever you install a group of plugins one by one just to find out which one can make your software work, you either haven’t gotten the right one, or have accidentally skipped the right one or it has become the last one installed.
  • No matter what problem you have with your computer – Its Always Microsoft’s fault
    Corollary: If its not their fault – Blame them anyway :-)
  • You will get disconnected from the Internet or experience a computer crash when you are downloading. If you don’t experience one within 80% completion, then it will happen at 99%. If you do manage to get the file, then it will turn out to be completely useless and/or invalid.
  • You’ll always receive an e-mail from a web site that you never visit before.
  • 75% of the bugs laws in this page can be applied to MS Windows (Any version).
  • Auto Correct – isn’t
  • Microsoft excel- doesn’t
  • If you need to shutdown your PC ASAP, It will restart.
  • The quickest way to shutdown a PC is to unplug it.
    Corollary: ACPI shutdown (sometimes faster to get to than the plug) does not always work.
    Corollary: ACPI shutdown will fail most frequently when you run the risk of being caught doing something.
  • No matter how big a hard drive you buy, you’ll need to double it in a year.
  • Complete computer breakdown will happen shortly after the maintenance person has left.
    Sent by Jan Wenall
  • A virus will be erased when the hard drive crashes, making it useless for antivirus program to fix it.
  • The problem always exists between one keyboard and it’s respective chair.
    (On submission problem was insomnia… zzzzzz)
  • A program that compile on the first run has an error in the algorithm
  • Edward V. Berard Law
    Walking on water and developing software to specification are easy as long as both are frozen.
    Sent by Andre Van Dun
  • The smaller the size of your email account, the more junk mail you will get
  • The boss will always come to your workspace when you accidentally open an adult link
  • The more pop-up screens you have, the more likely the boss will come by
    The last three laws were sent by Mark
  • A computer is only as smart as the person using it
  • If it ain’t broke, Overclock it!
  • If you’re in a hurry, your computer will crash, a hard drive will become corrupted, or your files will be erased. Any way, you’re screwed if you have a deadline.
  • Software Reliability:
    Investment in software reliability will increase until it exceeds the probable cost of errors.
  • Computer sadism: When the computer causes physical or mental damage to a person and can’t receive such a return favor (due to management rules).
  • Computer masochism: When a computer takes all the abuse you think you can give it and continues working as it should.
  • The sound of grinding metal or the sight of smoke coming from a case is a warning that you are trying to do too much with too little.
  • The survivability of a system is directly proportional to the price of the cooling system applied to it and inversely proportional to the amount of use it sees.
  • Antivirus systems only effectively work on a virus after given virus has passed its prime.
  • The most frightening of viruses is the virus you do not know is already there.
  • The amount of damage that a string of code can do is inversely proportional to the length of the string
  • You only receive instant messaging, when working on a project that’s due instantly
    Sent by Keith
  • When designing a program to handle all possible dumb errors, nature creates a dumber user
    Sent by Rich Spejcher
  • There is an inverse relationship between an organization’s hierarchy and its understanding of computers.
  • Pioneers get arrows
  • The smallest problems will immediately be brought to the attention of the CEO, but the big problems will be ignored until the affected system goes down.
  • Leet speak is nothing more than some poor fool’s attempt to type really, really fast.
  • Computers never work the way they are supposed to. Especially when nothing is wrong with them.
  • A program will work the you think is should only when you don’t care if it does.
  • Software does not fail when the technician is in the room.
  • as soon as you download a big file, your computer with shut down
  • The longer the e-mail, the greater the chance it will not make it to its detination, for whatever reason
  • If you were preventive enough to save a copy of anything, you will not need it. Therefore – Not saving a copy of anything is directly proportional to the value of the information lost and the amount of time invested in gathering and typing it
  • Proof-read all e-mails three or four times before sending it. All errors are detected immediatly after being sent
  • Murphy works for Microsoft. In fact, he is in charge of their QA
  • the chance to lose data is inversely proportional to the number people in the room when updating a simple server program
  • Good enough – isn’t, unless there is a deadline.
  • Don’t take it personally, stupid

(C) www.murphys-laws.com

Filed under: Howdy

What is Google Apps Sync for Microsoft Outlook

Google Apps Sync for Microsoft Outlook is a plug in that allows Microsoft Outlook to run on the Google Apps backend rather than Microsoft Exchange Server. End users can continue to use the familiar Microsoft Outlook interface for email, calendar and contacts as they transition to Google Apps.

Editions included:
Premier and Education Editions

Languages included:
Available worldwide with US English interface

How to access what’s new:
You can download Google Apps Sync for Microsoft Outlook at www.google.com/apps/get-outlook-sync.

For more information:
http://googleenterprise.blogspot.com/2009/06/use-microsoft-outlook-with-google-apps.html
fyki pls..

Filed under: Thought of the day , , , , , ,

The Neuro Science Behind What Makes Us Want

Neuro

 

In the growing field of Neuro Marketing, we’re beginning to understand the neuro science behind what appeals to a consumer from the primordial recesses of the brain. Susan Weinschenk, researcher and author of the book Neuro Web Design, What Makes Them Click?, is applying this principle to web design. She presented some of her findings at the Internet User Experience 2009 conference in Ann Arbor, Michigan. What an eye opener! 

In the study of human-computer interaction (HCI), we often look at cognitive psychology to understand what motivates a person to click. In fact, the study of HCI was born from cognitive psych. Weinschenk, however, points out that this goes deeper. Decisions are motivated not only by the conscience but also by the unconscious mind.

Weinschenk touched on three interesting principles. I’ll begin with the last since it’s the most exciting: the principle of social validation. If a user is uncertain about a decision, he or she will look to other people. Specifically, consumers trust peers over expert reviews or recommender systems. We, as web marketers, can apply this principle in smart application design and social media. Find and promote the community around a product and include credible reviews. 

Another principle is related to decision making and the number of choices presented. Users may say they want many choices, but the research presented in the book actually proves that the fewer the choices, the more likely a person will click — or better yet, purchase. Too many choices cause the user to freeze and make no choice at all.

The third principle presented was the fear of loss. It’s better to begin with all options and then allow the user to subtract. The fear of loss principle means that users are reluctant to remove options and more likely to purchase a product with premium options if that is what is first presented. An example of this principle in play is on Dell’s website. Products begin with more expensive options and the user can subtract these for a less expensive end product. 

Since all this happens on a subconsciousness level, it’s hard to say whether or not (as a consumer) I’ve actually acted this way during a purchase process. Still, I agree with Weinschenk’s conclusions. I’m eager to apply these learnings in my XA practice. I’d like to give users fewer and more relevant choices. Then integrate social media as a way to influence their decisions.

So the next time you make a purchase decision, think about what made you choose what you did. MR McGill

Filed under: Thought of the day , , , ,

Dance, Pump, And Charge

power-pump-d

Photos by Andrew Liszewski at OhGizmo!

Mobile operator Orange seems to have put together three of my favorite things – music, festivals and green energy – two years in a row. At last year’s Glastonbury Festival in the UK, Orange introduced a recharge Pod tent to keep mobiles juiced with 500-watt solar panels and a wind turbine. They also gave a few lucky dancers kinetic chargers called Dance Charge, which convert the dancers’ physical activity into electrical current with the help of a system of weights and magnets.

This year, Orange UK is getting ready for Glasto with the Power Pump. It’s a foot pump that drives a turbine, which powers a tiny generator. They say the turbine will generate enough energy to power five minutes of call time in a just a couple minutes of pumping.

Filed under: Thought of the day , , , ,

We’d Like Our Data, Facebook Please…

The great words of Joel Bauer… “it isn’t about being liked, it’s about being effective.”

Now I would argue that the greatest advantage today is in being both. In a time where our online social world is filled with endless noise, there is a lot competing for human attention. And as wrong as this may sound for some people, the truth is that in order to reach your audience (be them friends or colleagues)… it’s not enough to just be liked anymore, you have to be liked and effective.

We are all brands. We are all community managers.

But, that doesn’t mean that we have the budget or large staff employed at agencies or within brands to manage our online presence. No, we need to rely on useful tools to tell us the information we want to know, we need to know, and when we know it. Unfortunately, those tools don’t currently exist.

Why Social Networks Need To Embrace This
In the great big battle of social networks competing for our engagement time… it will be the networks that give us relevant feedback (who likes our posts, how many forwarded my link onto their friends) that will win our attention.

This isn’t so far off from what Obama discovered in his campaign for president, or what game designers have known for quite sometime: if you show people the progress of their actions, they will become more invested and engage more frequently. People like statistics, people like feedback, and people like to know that they are getting somewhere.

How Facebook and Twitter Can Offer More Value

What they can do immediately…
1. Give users access to the data they already collect. I shouldn’t have to have a fan page to know how interactions on my profile trend over time. What month did I have the most photo comments, wall posts, etc. You are already collecting that data, let me have it!

2. Integrate consistent metrics into the interface. Twitter’s big problem is that metrics are inconsistent and housed outside of their site. It would be nice to have an analysis panel that easily connects together my retweet ratio with the actual content that got retweeted.

What they can do in the future…
3. Base new functionality on what consumers want to know. There is already enough competing for our engagement. Facebook and Twitter don’t need to add more applications or functions. Instead they should help us gain a better understanding of the effectiveness of what we are already doing.

Social sites need to realize that consumers don’t want more widgets and feeds and doodads that add to our everyday noise. It’s time for networks to help increase the relevance of social content, by helping us become more informed party hosts.

Filed under: Thought of the day

 

July 2009
M T W T F S S
« Jun    
 12345
6789101112
13141516171819
20212223242526
2728293031