James Governor, @monkchips, makes some great points about UI design in his latest blog post. James discusses how Adobe is changing it’s toolchain to better support, endorse HTML5 and how open is a growth accelerator, not just a philosophical perspective. He get’s a useful plug in for the Dell Streak, and it as a piece of glass too 😉
I’ve alluded to it here before, we are heading in the same direction for both our PowerEdge 12g Lifecycle Controller and iDrac UI for one to one management of our servers; also for the simplified UI for the Virtual Integrated System, aka VIS. Flash/Flex/Silverlight had their time, they solved problems that at the time couldn’t be solved any other way. However, it was clear to me and I suspect to all those involved in the HTML5 standards efforts, that we were headed down a dead end of walled gardens“. What put this in perspective for me wasn’t James’ post, but one from fellow Redmonk, Cote, last year in which he discussed the web UI landscape.
![Web UI Landscape by [Michael] Cote](https://i0.wp.com/farm3.static.flickr.com/2453/3598148795_a5df425a44.jpg)
Web UI Landscape by Cote of Redmonk
The details actually were not important, Cote ostentatiously discussing
Apache Pivot, summarizes by saying “Closed source GUI frameworks have a tough time at it now-a-days, where-as open source ones by virtue of being free and open, potentially have an easier time to dig into the minds of Java developers.”
But really, it was the diagram that accompanied the article for me. It laid it the options as a flower, and as we know, flowers are grown in gardens, in this case, each was being cultivated in its’ own walled garden.
I cancelled the FLASH/WSMAN[1] proof of concept we’d built for the gen-next UI, and decided the right move was to adopt a more traditional MVC-like approach using open standards for our UI strategy.
We don’t have a commitment yet to deliver or exploit HTML5, but we’ve already adopted a REST style using HTTP for browser and HTML clients to interact with a number of our products, using Javascript and JSON and building towards having a foundation of re-useable UI artifacts. Off the back of this we’ve already seen some useful Android pilots.
Which takes us back to James post. He summarizes with “If the world of the API-driven web has taught us anything its that you can’t second guess User Interfaces. Someone else will always build one better. If you’re only allowing for deployment on one platform that cuts you off from innovation.” – Right on the money.
DISCLOSURE:
Redmonk are providing technology analysis for Dells Virtual Integrated System; James and I have professional contacts since 1996.
NOTES:
[1]WSMAN remains our key technology implementation for external partners and consoles to use to get information from the servers, and to send updates etc.
Recent Comments