Device capacity – the functional boundary expanded. I’ve talked a lot about the concept of the functional boundary- and in fact about its impact on the cloud solutions of the future. The next thing or consideration for me at least is the raw concept of capacity of devices.
I have a number of different mobile and not mobile devices. Each of the not mobile devices has a certain capacity or function. For example I use a box at home as an ORB server (don’t ask me why – I started doing it more than 5 years ago and just never really stopped). I have another box serving as a windows home server. It does the automated backups for computers on my home network.
Each box has a physical function and is on most of the time. It so happens that I can also use the processing power of those boxes via my iPad to reduce the stress on the iPad as far as processing locally.
The thing is, most applications today aren’t smart enough to say “hey you are using a portable device – do you want me to switch to terminal service mode – where we leave some of the processing on the host system.
Problem 1: smart applications that are aware of what you need, how you need it and the best possible delivery method.
Problem 2: solution awareness of my needs. IE where I am, what device and I using and in a tracking fashion what device might I use next to access the solution. It’s the old batch jobs from the mainframe days. They were set to run each night and you had information/data in your inbox when you got in the morning.What if applications and solutions were smart enough for me to kick off a job on my smaller smart phone device and produce it for me, the next time I log into a device with a larger screen?
There are many more problems and I will noodle through a few of them over the next few weeks.