ok…in hindsight, this post is just way too long…
As a budding technologist, I landed in a ‘sweet spot’ job in the mid-nineties. I was a web application developer for a wireless billing start-up. Sitting at the intersection of two rapidly growing technical ecosystems (dare I say ‘clouds’), I was part of a team that built an e-commerce and ebp&p platform for our wireless carrier customers…a ‘white label,’ online extension to our billing system. Part of our team was also responsible for building an e-business ‘wrapper’ around portions of a cobal based system running on SCO Unix. We were using J2EE as the framework with BEA in the middle and Oracle on the backend.
Our biggest technical challenges? An antiquated UI for the system itself (green screen), integration to other systems within the carrier business, and – most importantly data management for multiple millions of wireless customers – not only from a CRM perspective but also their usage, accounting for features, and accuracy of bills. We needed to be more interoperable, we needed to be able to scale, we needed to be more intelligent with the data we were managing (to help inform our customers about their own customers), and we needed to be more innovative.
These ‘needs’ led us down some exciting paths over the next few years. We tackled business intelligence to profile and analyze customer data. We leveraged Flash (4 at the time and following) to create a veneer for the UI (and looked at gaming interfaces as inspiration for our designs). We focused on the MVNO space to cover turnkey outsource billing, and we spent significant time digging into location based services, mobile marketing (find your target where they are) and personalization, stored value, real-time rating, near field communication and mobile payments. Many of these are still being baked today…
We considered the mobile device as a ‘lifestyle remote control’ and looked for more things to pull through it to the end user. For each service, we would look for a way to rate it. Likewise, we expected the environment to become more intelligent and give mobile devices more things to plug into. The Internet, we imagined, would sit behind those plugs and push content, provide meta data, process transactions, and foster rich communication among a global community of participants. At the core, experiential design and experiential engineering would drive innovation that we thought would bring these disparate ecosystems together.
Because of the many moving parts, however, most of these visions have taken long and evolutionary paths (unless you own all the moving parts like DoCoMo). Many are still finding there way due to the sheer number of participants involved in resetting such complex ecosystems. Either way, we were on the right track and I get excited to watch the evolution continue and to think about what’s on the horizon.
At the end of the day – getting to a point, I think – I was tickled to see this deck at OSBC a couple of weeks ago by Tim O’Reilly. He basically painted the reality of what we thought the world might be like 6+ years ago. I’ll save comments about the entire 98 slides, but for this post, take a look at slide 21 through about 67 where Tim outlines the convergence, via many examples, of the fluid integration of web and mobile ecosystems. As he states, the PC is out of the loop and the handset has become a sensory device for the environment. Lifestyle remote indeed…
- B