Welcome!

Microservices Expo Authors: Scott Davis, Stackify Blog, Elizabeth White, Kelly Burford, Karthick Viswanathan

Related Topics: Mobile IoT

Mobile IoT: Article

21st Century Wireless Tools: Working in a Networked World…

21st Century Wireless Tools: Working in a Networked World…

Companies are always risking their business, betting on what will be happening next year, and how they can make money out of it. The trick is to get it right.

We all know that we work in a fast-moving industry. Even before wireless communications raced ahead, the IT field was already moving too quickly for most industry commentators - fast enough in fact to make a fool of anyone rash enough to try to predict future developments.

From the famous IBM statement that the total world market for computers amounted to no more than 20 units, to Bill Gates saying that no one could ever use more than 640KB of RAM, history is littered with embarrassing comments on the future...and some more expensive errors of judgment. The Intel Web site makes no mention of the 80186, moving straight from the 80188 to the 80286; no one guessed at the time that backwards compatibility would be so important - something we now take for granted with every new development.

In the wireless world things are even worse, with companies staking their whole business model on the uptake of new technologies barely out of the lab. 3G networks really sum up this inability to guess what's happening next. No one knows what they'll be used for, but whatever it is, it's going to have to be expensive if the networks are going to turn a profit. It's remarkable that companies investing so much in future developments seem to spend so little effort trying to understand it, adopting the "If we build it, they will buy it" approach to development, often at a cost.

One company interested in what the future looks like is Xerox. If they could only turn their hand to making money out of their predictions, they could be dominating many diverse markets today. The Xerox Palo Alto Research Center (PARC) is trying to work out how computers and documents are going to be used in the wireless office of the future, how we'll interact with them, and what they'll do for us. You may have heard of Xerox PARC. They played a large part in developments such as the Graphical User Interface (GUI), Ethernet, and many of the Internet standards in use today. Their visions have helped shape the office you work in and the software you use, based on the point of view of the document as central, and everything else just tools to manipulate it.

Xerox doesn't always get it right. Many of their ideas are fanciful and far-fetched. Some are just too far ahead of their time, but some are becoming reality as we watch. One of these ideas describes the kinds of wireless computers that are going to exist, and how they can work together in a new kind of office. They're known as the Pad, the Tab, and the Screen.

The Pad
By examining how people work, looking at how they interact with the space around them, researchers at Xerox realized that we like to be surrounded by paper, or more accurately, by documents. The familiar desktop interface of modern computers bears very little resemblance to a real desk, with its piles of paper and printouts, handwritten notes, and scribbled details. We seem to like to work with our documents spread around us, not neatly displayed on a screen at eye level, but physically near us. The work we're most interested in is beside us, while work to be considered later moves to the side of the desk. Attempts to recreate this interface on a screen are, basically, laughable, and while larger screens may make us more comfortable with digital representations of documents, we still seem to need their physical presence to organize ourselves.

So the researchers considered how to make this digital, and decided that the solution was a large number of flat-screen wireless displays, each with a single document. When you sit down to work in the morning, instead of printing out your tasks for the day, you would bring up that document on a Pad, then probably place it on your desk. Another Pad might contain a printout of your current project status, while another has some slides you were working on, and yet another, some notes you made about future projects. These Pads would pile up around your desk - in the same way as the paper sheets there now - reminding you of things that remain to be done. Once a task is completed you'd clear the Pads involved with it, and they'd be ready to be used again.

Obviously, any Pad would be capable of displaying any document, but that isn't how they'll be used. Interfacing with the Pads would, most likely, be through a touch screen, but being wirelessly networked would mean that a keyboard or other interfacing method could easily be used.

Pads should replace the ubiquitous VDU on every desk, allowing a more natural way of working and preventing us from trying to fit our lives into a 17-inch screen.

The Tab
The Tab is a very small device, the size of a pager or wristwatch (it may even be a pager or watch, in addition to being a Tab). With only very limited display and interface options, the Tab offers only the minimum of document editing features. Tabs are more about people, and could well be built into name badges or corporate passes. They also have the ability to hold documents for transportation, and some may offer basic reviewing features.

Note that the Tab itself isn't considered to have much in the way of local storage, but always exists in a wirelessly networked environment. I might be working late, and decide to take some work home with me, so I transfer some documents from the Pads on my desk to my Tab to take home. When I get home I can simply transfer them to any Pads I have there, but the documents themselves never actually moved because a central server holds them. Only my perception of their location changes. If I lose my Tab on the way home no data has been lost. Though I may have some trouble finding it again, it's still there on the server. In this way all of the problems of multiple copies of files, and version modification, are addressed.

The Screen
The Screen is the simplest of our trio of devices. It's a large screen, probably mounted on a wall or other display surface. Networked in the same way as the Pads and Tabs, I would use a Screen to show work to colleagues or to give presentations. Displaying a document would be just a matter of copying it onto a Screen where I wanted to show it. Again, the document itself wouldn't move, only my perception of where it was located.

Obviously Pads, Tabs, and Screens constitute only the front end of the system. It should be obvious that such an environment is going to need a complex of back-end servers managing all the documents and ensuring that they appear to be where the users imagine them to be. The complexity of such a system shouldn't be underestimated. These devices would be very basic terminals, reliant on a server to carry out most of their processing tasks and only able to perform the most basic of functions without network connectivity. But such servers do exist, and network reliability has never been better. The servers are going to have to be able to talk to all the devices, all the time, and some form of standard wireless network is going to be essential. Xerox has done much work with infrared communications, though Bluetooth would now seem the obvious alternative.

It's when we consider the devices, themselves, that our technological limitations become obvious. The Tab is relatively easy - just mount Bluetooth into a watch and you're 90% there. The Screen is, similarly, easily created from a standard PC connected to a projector or plasma wall display, but the Pad is a more difficult challenge.

To get a letter-sized device, with a display of sufficient quality to read text from, and cheap enough for a dozen on every desk, isn't easy and perhaps isn't yet possible. Even ignoring the problem of needing to keep the cost down, the simple challenge of producing a device slim enough to be piled onto a desk, yet robust enough to survive a modern office environment, could well prove impossible without stronger materials or better manufacturing processes. The nearest equivalent would be the Web pads, as demonstrated at every consumer electronics show for the last few years, yet strangely absent from local stores. But these devices may well be overpowered for our needs, leading to their high cost and bulky size, and thus their lack of marketplace success.

Of course, it isn't necessary to implement the whole model to benefit from the ideas within it. What Pads, Tabs, and Screens are actually about is working with documents, rather than files or directories. The user experience is wholly document-centric and users don't need to know where the files are or how they're organized, just how to use them. The three devices described demonstrate the three ways in which documents are used, and attempt to describe devices that might fit each role perfectly, without users having to change their way of working to suit the machines. When any device can be used to access any information we'll really be working in a networked world. I'm looking forward to it.

For additional information, WBT readers can go to the fasinating Xerox Palo Alto Research Center Web site at: www.parc.xerox.com.

More Stories By Bill Ray

Bill Ray, former editor-in-chief (and continuing distinguished contributor to) Wireless Business & Technology magazine, has been developing wireless applications for over 20 ears on just about every platform available. Heavily involved in Java since its release, he developed some of the first cryptography applications for Java and was a founder of JCP Computer Services, a company later sold to Sun Microsystems. At Swisscom he was responsible for the first Java-capable DTV set-top box, and currently holds the position of head of Enabling Software at 02, a UK network operator.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
It has never been a better time to be a developer! Thanks to cloud computing, deploying our applications is much easier than it used to be. How we deploy our apps continues to evolve thanks to cloud hosting, Platform-as-a-Service (PaaS), and now Function-as-a-Service. FaaS is the concept of serverless computing via serverless architectures. Software developers can leverage this to deploy an individual "function", action, or piece of business logic. They are expected to start within milliseconds...
The cloud era has reached the stage where it is no longer a question of whether a company should migrate, but when. Enterprises have embraced the outsourcing of where their various applications are stored and who manages them, saving significant investment along the way. Plus, the cloud has become a defining competitive edge. Companies that fail to successfully adapt risk failure. The media, of course, continues to extol the virtues of the cloud, including how easy it is to get there. Migrating...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory? In her Day 2 Keynote at @DevOpsSummit at 21st Cloud Expo, Aruna Ravichandran, VP, DevOps Solutions Marketing, CA Technologies, was jo...
From manual human effort the world is slowly paving its way to a new space where most process are getting replaced with tools and systems to improve efficiency and bring down operational costs. Automation is the next big thing and low code platforms are fueling it in a significant way. The Automation era is here. We are in the fast pace of replacing manual human efforts with machines and processes. In the world of Information Technology too, we are linking disparate systems, softwares and tool...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies? We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measure...
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
"As we've gone out into the public cloud we've seen that over time we may have lost a few things - we've lost control, we've given up cost to a certain extent, and then security, flexibility," explained Steve Conner, VP of Sales at Cloudistics,in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Cloud4U builds software services that help people build DevOps platforms for cloud-based software and using our platform people can draw a picture of the system, network, software," explained Kihyeon Kim, CEO and Head of R&D at Cloud4U, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...