What can mobile app development teams learn from a spinning top?

Image

The left image was found in the Tomb of Tutankhamun, who died about 1323 BC. The two images on the right are contemporary, which means these tops were manufactured about 3300 years apart.

For many, it is hard to imagine a world when simpler, non-electronic, toys were the primary options for fun. How quickly we seem to forget!

IT and C-Level executives might be surprised to discover there are three business lessons that can still be learned from a simple toy like a spinning top.

Here are three for consideration:

Simplicity Can Increase Durability

Sometimes, the simplest concept can stand the test of time. Archeologists have found spinning tops that date back over five thousand years. And, here’s the most amazing stat: they still function today exactly as they did then. What about your mobile app? How will it stand the test of time? Is anyone taking bets that a cell phone, or any of its apps, will still be working five thousand years from now? How about one year from now?

Tipping Points

Without going into the physics of how a spinning top works, suffice it say that once a top is correctly spinning on a smooth surface, it will continue to do for as long as its’ spinning inertia can maintain a balance. Once inertia begins to slow, balance will falter, and the spinning top will revert back into being just an inert object. Eerily this description fits mobility software programs, too. Finding the right balance in software features and functions, without making it overloaded, may make the critical difference in the lifespan of the product. There are tipping points when all software programs stop being useful. And, an unused software app is another definition of an inert object. Have you identified your tipping points?

User Interfaces

A complex concept implies complex user interfaces. Plus, a complex concept has more points of failure than a simpler concept. A spinning top is an intuitive product. The very design of a top invites the user to give it a spin with a flick of the wrist. When users look at your mobile app, what is appealing and inviting about it? Is it intuitive or intimidating? Are users ready to give it a flick or a swipe to get started?

Final Thoughts

What are your best case hopes and aspirations for the life of your mobile app? A year? More than two years? More than five years?? Perhaps emulating the lessons learned from a spinning top will help produce positive influences on your mobile application projects. Aim high!

Author: HorneMobile

World Traveler. SME on supply chain software. SME on supply chain mobility.

2 thoughts on “What can mobile app development teams learn from a spinning top?”

  1. Software environments and business I think shift way more often. Even though, I agree that simplicity is the solution for deprecation and unstability, it’s paradoxically hard to find due to many factors. A spinning top behavior depends only on physics rules that haven’t changed that much in the last thousands of years, not to mention end-users (they still have two hands with the same size as inventors’ hands). I don’t think we have a good lesson in the analogy.

    1. Thanks for your comments. I think the tipping points could viewed as the primary analogy point. An overloaded app can quickly lose its balance and shorten its useful life span. My hope is that with planning one can have a better user experience and a longer life. Planning is the key!! I do like your comment about two hands. I am using two thumbs with my hands holding my cell phone. For a future blog topic, should there be a discussion navigation and best case keyboarding?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s