Tuesday, May 18, 2010

Web Design References: Usability

Benefits and ROI. (Why Usability?)

Up to Page Index

Children

Up to Page Index

Chunking

Up to Page Index

Consistency

Up to Page Index

Content

Up to Page Index

Definitions

Up to Page Index

Efficiency

Up to Page Index

Error Tolerance

Up to Page Index

Fitts Law

Up to Page Index

Flash Usability (see Flash page)

Up to Page Index

Forms Usability

Up to Page Index

Frames Usability

Guidelines & Principles (see Standards)

Up to Page Index

Homepages

Up to Page Index

Intuitive

Up to Page Index

Learnability

Up to Page Index

Line Length

Up to Page Index

Link Color (see Navigation)

Up to Page Index

Link Text (see Navigation)

Up to Page Index

Link Rot

Up to Page Index

Liquid/Elastic/Fluid/Fixed Design

Posted by bengeminii at 9:28 AM 0 comments

Sunday, May 16, 2010

IT now ET (Enterprise Technology)

Insteresting POV emerging as indicated in this Computerworld article.

This latest shifts in technology are disruptive enough that the ability to interconnect heterogenous devices and systems -- is far less strategic, just as the ability to write gigantic software packages became less important during the shift from MIS to IT.

Now the emphasis is shifting once again to technologies that extend and integrate with the physical world. Some characteristics of these enterprise technologies:

  • They involve some element of integration with the physical world. Examples: sensor networks, display technologies, smart grids, wireless monitoring devices. 
  • They are real-time. 
  • They involve large to very large amounts of data 
  • They can often be used to control -- not just monitor -- the physical environment
  • They are intrinsic to an organization's business. 

This will present new challlenges for IT leaders as the embrace the transition's gatekeepers - strategic ET and legacy (commoditizing) IT.  These are the challenges I like.

Posted via web from bitpakkit

Posted by bengeminii at 11:58 AM 0 comments

Friday, May 14, 2010

Mockupitis

Gem from Jay Rogers on the IXDA forums today:

*Mockupitis*  Pronunciation: \ˈmäk-ˌəp-ˈī-tÉ™s\
Function: noun

*1 :* The tendency of a UI mockup to make assumptions about design 
constraints based on poorly-chosen sample data used in the static wireframe, 
photoshop comp, or interactive prototype. Short labels that fit neatly into 
the space provided for them, evenly-dispersed text, small numbers of columns, 
orderly and strangely regular tabular data, convenient numbers of items in 
lists that happen to fit just precisely into the page, the list goes on. This 
tends to reduce the design to a limited visual exercise instead of exercising 
its ability to handle more realistic formations of user data.

ed. note: See also: "UX is not design, but parts of it look a lot like design"

Posted via web from bitpakkit

Posted by bengeminii at 11:51 AM 0 comments

Nerve juice


Data Transmission - DT-TV: D.Ramirez Gear Review #2: Nerve on muzu.tv

Posted via web from bitpakkit

Posted by bengeminii at 11:11 AM 0 comments
Labels:

Not such a great experience after all.

Nothing to see here.  Move along...

Just noting that Microsoft's UX evangelist site ux-strategy.com presents an interesting new welcome screen.

 

 

Posted via web from bitpakkit

Posted by bengeminii at 10:46 AM 0 comments

Sunday, May 09, 2010

Web 3.0?

Web 3.0 from Kate Ray on Vimeo.

A story about the semantic web by Kate Ray, featuring interviews with:

Tim Berners-Lee
Clay Shirky
Chris Dixon
David Weinberger
Nova Spivack
Jason Shellen
Lee Feigenbaum
John Hebeler
Alon Halevy
David Karger
Abraham Bernstein

Posted via web from bitpakkit

Posted by bengeminii at 2:34 PM 0 comments

Saturday, May 08, 2010

The value of nothing

 

 

“This is a deeply thought-provoking book about the dramatic changes we must make to save the planet from financial madness” — Naomi Klein. Opening with Oscar Wilde’s observation that “nowadays people know the price of everything and the value of nothing,” Patel shows how our faith in prices as a way of valuing the world is misplaced.   He reveals the hidden ecological and social costs of a hamburger (as much as $200), and asks how we came to have markets in the first place. Both the corporate capture of government and our current financial crisis, Patel argues, are a result of our democratically bankrupt political system.

If part one asks how we can rebalance society and limit markets, part two answers by showing how social organizations, in America and around the globe, are finding new ways to describe the world’s worth. If we don’t want the market to price every aspect of our lives, we need to learn how such organizations have discovered democratic ways in which people, and not simply governments, can play a crucial role in deciding how we might share our world and its resources in common.

This short, timely and inspiring book reveals that our current crisis is not simply the result of too much of the wrong kind of economics. While we need to rethink our economic model, Patel argues that the larger failure beneath the food, climate and economic crises is a political one. If economics is about choices, Patel writes, it isn’t often said who gets to make them. The Value of Nothing offers a fresh and accessible way to think about economics and the choices we will all need to make in order to create a sustainable economy and society.

Find The Value of Nothing online at: Amazon.com, Amazon.co.uk, Barnes & Noble, Borders, & IndieBound.

 

Posted via web from bitpakkit

Posted by bengeminii at 2:23 PM 0 comments

I had no idea Apple had their own version of a pesky client runtime

I hate to think that all that postulation and chest-beating took place from Apple with regards to their stance on Flash took place just to help advance the cause for something exactly the same as Flash, just different in that it was created and owned by Apple.  I thought it was all about HTML5, which made even less sense to me, now that I think about it.

But it appears I need to rethink everything: http://bit.ly/cCKCSc According to AppleInsider, Apple is using Gianduia, its new a client-side, standards based framework for Rich Internet Apps, to create production quality online apps for its retail users.

We arleady have web apps looking and behaving like desktop apps and the other way around, cross-platform systems relying on Air/Flash (and even Gianduia - will it be cross platform?) to look the same regardless of the underlying platform, and of course there many companies establishing their own experience and brand guidelines to push product families on any platform or technology.

The rigid unification of a computer based on some standards of the operating system, and the adaptation of every control to match the platform is a thing of the past. If this development helps people using digital products is another question - but it's definitely the development that I still see way too often in daily practice (Adobe Browser Lab is proof, no?).

The usual suspects deliver many examples of this: Google Apps, iTunes or Facebook do not really match operating system standards at all. The obvious approach is to make a good product, be consistent when it supports an overarching experience, innovate where it makes sense, and try not to break ANY environment.

Each case is different.  But clearly a client runtime is a great idea even if it seems like the wrong time in our digital evolution to fight over which one. If it was me I think I would choose one that has partners.

 

Android Smartphone Playing Adobe Flash Video = Awesome from Dave Meeker on Vimeo.

Posted via web from bitpakkit

Posted by bengeminii at 9:56 AM 0 comments

Friday, May 07, 2010

The merchant of mediocrity

Posted via web from bitpakkit

Posted by bengeminii at 8:08 AM 0 comments

Thursday, May 06, 2010

A Fourth Value for an Identity Pattern in Three Parts

I was on a thread today regarding the use of screen name or username as a way of identifying a user. Clearly there are patterns, or maybe one pattern with variations, in web application design that revolve around user identity management.

This confusion is compounded by using online services, such as Google, Yahoo!, eBay and other services who have established their identity models based on engineering-centric requirements.

I came across a great post in the Habitat Chronicles that essentially documents the historical belief that lead to conjoining the requirements of engineering (establishing sessions, retrieving database records, etc.) with the users requirements of recognizability and self-expression. But, this approach can actually discourage participation due to the fear of exposing personal data.

Yahoo! where I used to work found that users consistently listed that the fear of spammers farming their e-mail address was the number one reason they gave for abandoning the creation of user created content. This feedback ultimately led to the very expensive and radical re-engineering of the Yahoo identity model.

The author, Randy Farmer, found that a tripartite identity model would describe the needs expressed by most online services and more importantly, would be forward compatible with current identity sharing methods and future proposals.

He diagrams this most efficiently as:



Randy Farmer's Tripartite Identity Pattern postulates that the three components of user identity are: the account identifier, the login identifier, and the public identifier.

Read more about each of the elements and some interesting feedback on the pattern here.

Another interesting pattern in this regard is the use of a claims-based identity model. This revolves around the idea of claims i.e. a piece of information about an individual that is in doubt and must therefore be proved. Using an identity model based around claims allows individual identities to hold many disparate roles which can relate to different organisations as part of a wider ID metasystem. The way in which these claims are asserted and proven can be handled by a variety of technical solutions and services.

Microsoft's (where I also used to work) ASP.NET team documented the Geneva Framework as used for building claims-based applications and services for ASP.NET applications. Features include:

  • Security Token Services (STS)
  • Federated authentication from ASP.NET applications
  • Object Model that facilitates claims-based authorization form ASP.NET applications

The above definition was taken from the below URL, this webpage also gives a more in-depth look at what is a claims based system is and how the Geneva framework fits in.
http://msdn.microsoft.com/en-us/magazine/dd278426.aspx

Microsoft's Passport service which I worked on for a few years at Microsoft is a good example how this can work to provide identity services between applications.

Who Cares? Where is this going?

Federated and open identity systems ultimately lend themselves to a new identity pattern that I have yet to see documented, but I actually think I see it in use quite frequently, mostly when I comment on blogs. Frequently the comment I post is able to retrieve information such as username or real name and an avatar without ever exposing personally identifiable information that could be used for rude behavior such as spamming or harassing someone. However, what strikes me as the untapped potential in this emerging pattern is the concept of 'ownership' of my contributions as it relates to the persistence and distribution of that identity.

Activity as a function of Identity

If there were a fourth element to the tripartate identity that was activity this would complete the social pattern. I could consume or represent that identity in the context of contribution, content or context as appropriate and as subscribed to by the user who owns the activity and identity.

This would enable a double-click on an identity that could perform interesting new social functions:

  • Aggregate user output in the context of an experience essentially allowing me to view contributions of an individual expressed as an identity
  • Assimilate interest and behavior and express this as a contextual metaphor (e.g. a score, a weighting, etc)
This is actually already taking place in emerging social networks and leading edge news/blog sites and in my opinion brings new value to the definition of identity.

...to be continued.
Posted by bengeminii at 10:26 AM 0 comments
Labels: , , , , ,

Another UI Patterns Collection

OH: Platform-agnostic user and customer advocate seeks patterns to make sense of web apps.

UI Patterns is a self-proclaimed growing collection of User Interface Patterns that someone has started collecting from web sites (and a few applications). This anonymous developer has begun collecting under the following subheads.
Posted by bengeminii at 9:39 AM 0 comments
Labels: , , , ,

The control panel

If you want to be in control, you might need a panel.  I have been thinking a lot about control panels in UX/UI terms and the real-life and historic examples of this are an inspiration sometimes.

Posted via web from bitpakkit

Posted by bengeminii at 9:28 AM 0 comments

This video commerce thing...better than in-store?

Summit says yes...

In the replay presentation below, Summit Sports talks about how they doubled online revenues after incorporating enlarged images, alternate views and zooming capabilities (from Adobe Scene 7) and then actually captured more than 1,400 product review videos in just three days, basically giving them a total of 3,000+ videos to help explain and sell its gear and equipment.

You have to register to watch it, but Dennis Kopitz, Director of Web Development for Summit Sports Inc. makes a good case for going this route saying that it is actually better than the in-store experience.

Check out the store and grab that wakeboard I've always wanted at http://summitonline.com

Posted via web from bitpakkit

Posted by bengeminii at 7:17 AM 0 comments

Wednesday, May 05, 2010

HTML5 Web Experience on iPad

I guess it will be better later.

 

Posted via web from bitpakkit

Posted by bengeminii at 5:13 AM 0 comments

Tuesday, May 04, 2010

Customer Process Management

(Disclaimer: Since I heard so much about CPM being dead as a pricing model I would like to reclaim the acronym for something useful)

There are no shortage of business process management professionals, businesses, problems, platforms, analysts, books, theories, architectures and general products and services. People have spent years building up massive practices and businesses and used this BPM terminology in order to help move us from the archaic world of database and legacy-centric thinking that has built monolithic applications and waterfall-en methodologies around core business processes. We managed the unmanageable by wrapping management capabilities around the processes and exposing this management layer to the various users who ultimately owned or had to interact with those processes.

We wrapped our lingo franca up with some analytics, intelligence, integration points and made sure that we could deliver this in some useful fashion. We integrated to service buses and SOA back ends, consumed REST and SOAP endpoints, dressed it up in Flash and AJAX and pushed these processes out to users and yes, even customers.

And so at some point, we actually blindly entered a space where we had customers managing their view of business processes. We had dressed up these business processes with some kind of front end and exposed appropriate elements and touchpoints of those business processes out to customers. We had customers managing processes. But the business owned the process right? They owned the outcome right? It ultimately benefited the business right?

Now we have added Social BPM - the latest shiny object in the information workplace - social collaboration around the business and associated business processes that require new levels of collaboration. That collaboration also apparently, from time to time, may involve customers.

Don't customers (don't we) have our own processes? Actually we also have the ability to manage our processes too. But, unfortunately noone is exposing any Customer Process Management endpoints for us to consume, use, interact with or ultimately use to do the things we want to do.

I want all vendors to please submit their products and services to my 'vendor selection process' - please compare your prices, service levels, warranties, etc in a standard way so that I can consume these into my selection process.

Once I have completed my vendor selection process, please supply the product or service at appropriate intervals for the agreed upon price. Submit any variations in service level, quality, timeliness, friendliness, or things I may not have thought of to my vendor evaluation process.

When I love you and what you do and refer you to a friend, please accept my consumption of the 'mimic me and don't fail' service together with my 'these guys are good' service to ensure a constant fidelity with your new service endpoint based on expectations set in my instance.

Is it just a subtlety, or is there a notion where we as consumers could own our processes, could force endpoints to be met in terms of an SLA and commitment as a condition of doing business? I think we are in control of the money that gets spent and it seems to me that all too often we let inconsistent service, poor pricing practices, overt marketing attempts for upsell and cross-sell to ultimately impact our perceptions of quality but we carry on disheartened but stalwart in our willingness to compromise and let business fail at our expense. What choice do we really have? We have self selected into a business process and are now inserting coins in the slot to keep the monkey dancing.

Imagine, with me, for a minute a world inverted and built in our favour, where those who want our money, loyalty and commitment ultimately meet us on our terms.

OK, back to work...and go ahead, keep CPM for whatever you were using it for already.

Posted via web from bitpakkit

Posted by bengeminii at 1:15 PM 1 comments

Wednesday, April 28, 2010

Like. Social Shopping.

Posted via web from bitpakkit

Posted by bengeminii at 6:54 AM 0 comments

Tuesday, April 27, 2010

Tubby Toast

OTTAWA - Two random thoughts collided on the internet today causing a devastating urge to write down the following nonsense.

I have been reading this very insightful paper called "Attuning Notification to User Goals and Attention Costs" by D. Scott McCrickard and C.M. Chewar which is all about trade-offs we need to make in notification systems in order to support user access to additional information from sources secondary to their primary activity.  In parallel I have been looking into indexing and mapping strategies that best resemble classification schemes, such that a developer could actually surface best practices to the UX layer as a catch-all for 'everything that is possible".  Somewhere in between these two extremes for navigation and interruption is the actual paper I am working on with a few colleagues around defining all of these patterns of interaction in an attempt to create better dialogue, more utility in taxonomy and agility in the way we address interaction layers.

While on the trail of classification I came across a brilliant new post from Donna Spencer called Classification Schemes (and when to use them) http://bit.ly/cOWowu and within that she talks about best practices for classification inclusive of good old-fashioned Alphabetical indices and some great insight in terms of the opportunity to educate and inform users even within this seemingly mundane approach to experience.  As any good author would, she cites a few examples and her example of a best practice in this regard is the BBC "A Whole Lot More" function which is essentially an alphabetical listing of all their sites aptly located at http://www.bbc.co.uk/a-z/.  BBC provides the alphabet linked across the top nav element of that page and uses the remaining real estate to showcase Categories and enables horizontal scrolling of that category.

And here comes the collision...

On that categorical horizontal scroller I was drawn immediately to the lower right of the page (I assume I must have already adequately inspected the top left) wherein I was greeted by the familiar (I have children) waving form of the purple Teletubby, Tinky Winky.  Tinky Winky, unlike the other characters featured more demurely, even sombre and moody, in their category boxes was smiling, animated, welcoming and engaging and I realized he was hogging my attention on the page.  For those familiar with the Teletubby cartoon, you will know that they do things that little children like to do, such as rolling on the ground, laughing, running about, and watching real children on the televisions embedded in their stomachs.  Their stomachs accept one form of substance, a waffle-like form that ejects vigorously from their readily available toaster called Tubby Toast.

And that's when it struck me.  Henceforth, overexuberant notification systems that dominate attention span in an unbalanced way will always be referred to as Tubby Toast.  That's it.

Thank you, Interwebz, for this unique form of conspired inspiration and the ability to share it.  Hopefully you were notified of this article's existence in a usual, predictable and friendly fashion that gave you latitude to continue with your original task.

If you were looking for information on actual Tubby Toast, you can learn how to make your own here: http://www.pbs.org/parents/birthdayparties/teletubbies/food_toast.html but bear in mind you will be hard pressed to use that for any form of digital notification system.

 

  

Posted via web from bitpakkit

Posted by bengeminii at 12:56 PM 0 comments

Monday, April 26, 2010

A play on violins

Violin sculptures from Phillipe Guillerm.

Posted via web from bitpakkit

Posted by bengeminii at 11:31 AM 0 comments

Y?

Who spends more time on Facebook than they do with their family?

Who has played more than 5,000 hours of games and sent more than 250,000 emails?

 

 

Wei Liu is a designer, studying interaction design in Amsterdam, and is looking for people to share experiences and ideas that relevant to his research. If you would like to share your thoughts with Wei, please input/discuss your thoughts on http://generationyinteractions.blogspot.com/  where there is already some interesting things posted. He is especially looking for your input for the following questions:

a) What are the characteristics/classifications of 'Generation Y'?
b) What are the relevant trends/opportunities in interaction design?
c) How to map these characteristics into the development of 'Generation Y' interface?

That's Y.

Posted via web from bitpakkit

Posted by bengeminii at 8:46 AM 2 comments

Thursday, April 22, 2010

Adobe Cloud Computing - LiveCycle ES Cloud instances

Original post on: http://technoracle.blogspot.com/2009/01/adobe-cloud-computing-livecycle-es.html

In case you missed the news on January 12, Adobe is now offering Adobe LiveCycle ES Developer Express. This is Adobe's first (but not last) major foray into the world of enterprise cloud computing. The LC ES Developer Express software is a full version of Adobe LiveCycle ES that is hosted in the Amazon Web Services cloud computing environment and provides a virtual, self-contained development environment where enterprise developers can prototype, develop, and test LiveCycle applications

Feature set?
  • Provides pre-installed, pre-configured virtual instances of LiveCycle ES.
  • Reduce time required to download, install, and boot new server instances.
  • Develop LC ES applications in a fraction of the time.
  • Virtual instances can be used to build proof-of-concepts

The base installation provides the following LiveCycle ES server applications pre-installed:

  • LiveCycle Forms ES
  • LiveCycle Reader Extensions ES
  • LiveCycle Rights Management ES
  • LiveCycle Barcoded Forms ES
  • LiveCycle Digital Certificate ES
  • LiveCycle Output ES
  • LiveCycle Process Management ES
  • LiveCycle Content Services ES
  • LiveCycle PDF Generator ES
LiveCycle Production Print, LiveCycle BAM, and LiveCycle PDFG 3D are not included in this installation. In the Developer Express installation, LiveCycle is running on the JBoss application server and the MySQL database. The first screenshot below shows one of my three instances up and running:



Once you get an instance up and running, it appears to be virtually running on localhost:8080. There is a small download called LiveCycle Developer Express (shown below), which then allows you to log in to the instance running in the cloud.

Once you log in, select the instance:

and hit "Connect". Once you connect, you will be able to log in by accessing the admin panel via a browser. The URL is http://localhost:8080/adminui/secured/admin.faces. Note below that I am now logged in as Admin while running it in the cloud from my Mac. What does this mean? LC ES on the Mac!!!


From here you can browse all running services on the instance:


or manage endpoints:


The service, available to all members of the Adobe Enterprise Developer Program, allows developers to bullet-proof their applications without having to invest in a development environment or test lab. I will be unveiling more on a future episode of Duane's World when we get into SOA and ESB cloud architecture.

UPDATE: There is now a full video tutorial posted on how to work with the cloud offering here: http://technoracle.blogspot.com/2010/04/using-livecycle-es2-on-cloud.html


My Photo
Author: Duane "Chaos" Nickull (pictured) is an Adobe employee and lifelong musician, cynic, traveler, athlete, author and first class antagonist.

Posted by bengeminii at 12:30 PM 0 comments

Sunday, April 18, 2010

Detritus

Digital Detritus - Earth from Peter Root.

Posted via web from bitpakkit

Posted by bengeminii at 2:03 PM 0 comments

Ephimicropolis

The making of Ephemicropolis from Peter Root on Vimeo.

Posted via web from bitpakkit

Posted by bengeminii at 1:57 PM 0 comments

Saturday, April 17, 2010

Experience

Wordle: Flash Platform Experience

An example of how Java can effectively support Flash ;-)
Posted by bengeminii at 11:28 AM 0 comments

Friday, April 16, 2010

iPhone still tops for mobile ads

Recent TechCrunch post with stats from Millenial Media indicates continued "leadership" for MacOS devices in terms of mobile ad delivery. iPhone was seconded only by other Mac devices, but it was interesting to see RIM in the overall #2 spot, which seems to prove that they have broken into the consumer/end-user space quite aggressively.

Posted via web from bitpakkit

Posted by bengeminii at 7:30 AM 0 comments

Thursday, April 15, 2010

UX Sense...

Since so many UX posts still focus on "what is UX" or "why is UX" and the plethora of posts are starting to cement a broader awareness and general understanding of UX craft, I wanted to help out and lend my take on things. Maybe its just a baseline for this blog, or perhaps it will help someone starting out.

User Experience put simply makes things easier, better and more valuable for the end user. Often motivated by simply enabling the accomplishment of goals (the light is green, you can go now) a user experience professional should be the best and most vocal user advocate on the team, carefully balancing business goals, technical / development limitations and organizational requirements to ultimately support this new and pure focus on the user.

Following some semblance of a process and path iteratively, UX teams will build knowledge, manifest options and refine implementations together with all the other stakeholders and craftspeople in the mix. In general these steps towards a well lit path are as follows:
  1. Conduct user research to understand the requirements, painpoints, ethnography and psychology of the end user. You may already have a raft of input and usability drivers based on previous versions of the project or what other people are doing in similar situations. For example, if you are working for a bank, learn from your own banking experience or perhaps conversations with family and friends about how their experiences are good, bad or ugly or even awesome. These emotional insights can be golden.
  2. Identify aspects of the driving business strategy that can be articulated to clearly define user profiles, scenarios, and their importance to other stakeholders in order to capture all the necessary requirements and validate them.
  3. Seek to understand, imagine and document the various outcomes, starting with users themselves, but also with appropriate evaluation and inputs to project managers to estimate, the developers to build, marketing teams to educate and communicate, partners to evangelize, sales to sell, support teams to help out, etc...this may take the form of wireframes, documents, whiteboards, presentations, whitepapers, napkin sketches, meetings, phone calls, obsessive ranting or lucid dreams (okay, I'll stop).
  4. Iteratively design the functionality, interface and interaction of the various required visual components, focusing on standards (e.g. brand usage, standard iconography) and usability notions such as feedback, performance and outputs. A best practice at this time is to involve users, stay in constant dialogue with development teams and continually gain buy-in from business teams.
  5. Often once the iterative step is mature UX pros may come up with a well designed functional prototype and once again iteratively test it for usability flaws.
  6. Project Managers should now be ranting on about versioning and release dates and timelines for developement cycles, indicating their comprehension of effort and direction ;-) You may agree that it is important to document every single point observed from the initial user research to how it shaped the product and how it has been taken into account.
  7. Once a version is ready, we conduct more usability testing now ensuring that the test scores perfectly against the output of the initial user research findings.
  8. As we conduct this last round of testing we evaluate and validate the relationship between the product and its supporting materials - documentation, FAQs, How-To, Quick Stat Guides, Tips - for consistency of experience and language
  9. Once the product is relased, keep an eye on forums, blogs, and any kind of structured or unstructured feedback and statistical or behavioral analysis that will reflect the solutions user experience maturity and inform necessary iterations as we move forward.
  10. Now we post the story about our work, what we did, get our talk ready for Adobe MAX, or get the screenshots and customer quotes ready for our book ;-)
This may not be all the steps and I have deliberately avoided complex or hardened methodologies typically proven out over long periods of time in well-established teams. This is more about what you can do, how you can go from having an interest in what UX is to actually doing it on your next project and helping to grow your business by investing in one of its best assets - customers or users and how much they love using your products or services.

Finally I would prefer to go over this article and replace every instance of USER with the word PEOPLE, but that's another story.
Posted by bengeminii at 12:10 PM 0 comments
Labels: , , , , ,

Monday, April 12, 2010

Best Snowboard Tricks

Best tricks "landed" - that's always good.

Posted via web from bitpakkit

Posted by bengeminii at 5:28 PM 0 comments

Collaboration=Conversations

It is interesting to read through this presentation through the lens of corporate collaboration or collaborative applications...
Crucial Conversations In Social Media
View more presentations from Kelsey Ruger.
Posted by bengeminii at 1:54 PM 0 comments

Friday, April 09, 2010

iMonetize Everything


iDoit with iAd. (not me personally of course)

This image on the right linked from MobileBeat article provides a more balanced view of the story than my conjecture and opinionated blast below.

Apple's mobile strategy brilliantly accomplishes what so many startups try to do - build a massive, loyal, captive market before fully monetizing every single little thing that market does - iAd confirms that this strategy remains a pretty brilliant move!

The fact that most people don't get why iAd is so brilliant makes it even more brilliant - Apple needed to get past the top of the adoption curve, move beyond fanboys into the mainstream, in fact turn a phone into a fashion accessory and status symbol (again), without an ad play in the public eye that would massively reduce credibility of the platform in the early days.

Once they had the platform at critical mass, and had locked down all the inroads, then they were able to release an at-scale ad play to further monetize the distribution. And they can now make a % of every click, impression or scene change in their own proprietary version of rich media.

This also provides another clear reason (more clear than most of the B$ and raving lunacy that's out there) why they did not want Flash on the platform - motivated app developers could have easily served up their own in-context, targeted or even DoubleClick and Yahoo! served ads over video, in-game, or within web-based RIA applications without ever clicking the Apple clock. The only players that really matter who are targeting the Apple platform today are getting bought, or soon will...

The good news is that this move will increase the credibility and overall percent spend allocated to mobile, but there will be some work to do since big advertisers/agencies will continue to favor existing formats and ad serving, auditing and reporting technology to deliver integrated campaigns (cross-media) for some time.

Apple knows this and will likely posit for the high-end of the CPM/CPA target - but in a frequently sold-out market the more floor there is (bottom pricing/wide avail) the more value they can bring as the user base becomes more addressable, and if they get their targeting (geo, gender, income, interest, behavior, spend pattern) sorted out for a captive audience then they will start to dominate (at least on their own platform).

Basically, if iPhone came with an ad platform story three years ago everyone would have cried foul. And if they had allowed other platforms in they would give up a portion of dollars beyond the platform and app that they knew (and so did everyone pretty much) would be forthcoming.

I love Apple, don't get me wrong - I love any brand that has a great user experience and works that hard to maintain it across platforms but I see cracks in the bauble that are somewhat worse and somehow seem even more dangerous than the roadscars on my MacBook Pro (but that's another story).
Posted by bengeminii at 8:50 AM 1 comments
Labels:
Subscribe to: Posts (Atom)