Sybase Business Intelligence Solutions - Database Management, Data Warehousing Software, Mobile Enterprise Applications and Messaging
Sybase Brand Color Bar

Posts Tagged ‘Mobility’

How Top 3 Mobile OSs Will Keep Innovation Alive

January 25, 2012 in Uncategorized | Comments (0)

Tags: , , , , , , , , , , , , ,

Its always tempting, at the beginning of a calendar year, to cast a glace over the last twelve months and see what another trip around the sun has brought us. When I read this article about global smartphone adoption, I definitely got something that has been on my 2012 forecast: We are on the way to having a few strong players in mobile OS race.

The jury is in after Monday’s news. RIM has taken a tumble and is unlikely to regain market share or its formerly decisive position of leadership in smartphones. The company’s recent misadventure with their Playbook tablet device cost nearly half a billion in write downs. Even more seriously, RIM’s smartphone market share is off by two thirds over the last year, with Android eating most of their lunch. At the same time, Nokia and Intel have abandoned efforts to create a Linux-based mobile OS. Don’t misunderstand. I don’t dislike Linux and have owned several BlackBerrys (which were great devices in their time). I find no personal pleasure in RIM’s misfortunes. However, the enterprise mobile space desperately needed a shakeout in mobile OSs.

Together, Android and Apple’s iOS have amassed sufficient share to exercise a beneficial kind of dominance. As software developers and device innovators organize around these two OSs, de facto standards can emerge. This coalescence creates a rational, sustainable tech market landscape. Having a couple of strong mobile OS players will keep innovation alive, hold prices in check, and let consumer demands drive device development. By the same token, having only a couple of strong mobile OS players concentrates software development talent and allows skilled labor pools to grow. This will provide enterprise much greater opportunity to attract in-house mobile app development professionals. And building in-house enterprise app development resources allow a line-of-business manager or IT group can put forth mobile initiatives that cover 70% or more of the US smartphone installed base and can be accurately scheduled and costed. This may be a watershed moment for enterprise mobility.

Tips to Responding to Disruptive Change on Friday the 13th

January 13, 2012 in Uncategorized | Comments (0)

Tags: , , , , ,

I’m just guessing here, but for the average dinosaur, the year before the big asteroid hit the earth and wiped out most life forms, it probably didn’t seem like that big a deal that some of the stars in the night sky were steadily getting bigger. Then, yoicks. Hello disruptive change, goodbye brontosauri.

Enterprise IT is on the threshold of disruptive change, but in the present instance, there will be a lot more rearranging and a lot less extinction. This is not something that people haven’t been talking about. Mobile devices, and particularly employee supplied mobile devices, are rapidly wresting control of budget and decision making from monolithic Information Technology departments. Consider this:
• Today, more than half of all enterprise mail is received via web mail, often accessed by tablet or smartphone, as opposed to a desktop based email client.
• Enterprise Mobile app development is projected to outpace desktop targeting app development 4 to 1 by 2015.

We can already see enterprise IT realignment taking place. Highly centralized IT departments are losing staff, budget and Solomonic discretion over what software and hardware tools enterprise users adopt to do their jobs. Line of business managers and even individual employees are doing more independent decision making about sourcing technology. If you stop reading here, the story sounds bad. But it’s not. At least, not mostly.

Remember how the big, bad asteroid story actually ended? Pruning away a lot of enormous, sharp toothed, ravenous reptiles made it possible for bunnies and ponies and – hold onto your hairnet—people to emerge. Likewise, CIO-lead organizations and IT professionals will evolve, thrive, and endure. Here’s why: While the shift to mobile device based business processes certainly makes users’ lives better and can make businesses more competitive and adaptive, enterprise mobility can neither invent, manage, nor support itself.

At enterprise scale, the mere fact of mobility doesn’t make technology simpler to integrate, secure, or manage for returns on investment. Count on it: A year from now, we’ll be reading cautionary tales about what happened when some company simply turned out the lights in IT and let users fend for themselves, BYOD style. Chaos isn’t very accountable, but unfortunately, anarchy does scale pretty well.

There has never been a better case to be made for adequate and intelligent mobile technology management. Going forward, I see enterprise IT departments being reformatted as consultative organizations with strong mobility biases. In-house mobile IT experts will:
• Help users make sourcing decisions for cloud services, mobile solutions and the like;
• Develop custom mobile solutions for tablets and phones;
• Assist in creating customer facing engagement and brand building experiences; create and manage enterprise app stores;
• Be tasked with myriad other very complex, mission critical functions.

There won’t be any time left over to lament all of the cumbersome centralized IT technology that passes into the cloud or the fossil record. However, nostalgia isn’t completely out of the question. Perhaps someday there will be a kid’s TV program starring a mainframe. It’s not impossible. Barney got his own show.

All I Want for Christmas is A Million Mobile Apps

December 19, 2011 in Uncategorized | Comments (0)

Tags: , , , , , , , , , , , , ,

According to India’s Financial Chronicle, somewhere about the end of December 2011, there will be over 1 million mobile apps available in the public marketplace. India’s largest mobile app store, Mobilewalla, says that currently about 15,000 mobile apps are released weekly. Just to put this in perspective, there are something like 3.2 million physical books in print as of today. If you use the beginning of Johann Gutenberg’s printing operation in the 1480’s as T=0, the weekly average for global print book publication over the intervening 530 years comes out to about 115 per week.

This is one case where no one is going to say “You do the math”. It’s a complete waste of time to do the math. There is very obviously a tsunami of mobile apps washing over the globe, literally the biggest worldwide personal empowerment movement in the history of life on earth.

If that assertion seemed a little bit breathless, fear not. I am about to take a step back from it. First, I will heartily acknowledge that, far and away, the largest app category is comprised of games and entertainment. Don’t be fooled by this. While it may not be of tremendous enterprise import that 15,000 apps a week are being released if 14, 550 of them are a variation on Angry Birds, here’s what is important. Mobile apps are occupying a place in popular culture that can’t be ignored or dismissed by IT professionals, because they represent a complete shift in people’s expectations about connection and engagement.

If you doubt this, remember that we have seen the same communication technology paradigm shift play out several times before: Recall once-novel capabilities like voice mail, fax machines, email and web presence. The tipping point for business occurred when similar technology became available to consumers. If people had access to a technology at home, it automatically became unthinkable to them that businesses wouldn’t provide voice mail, fax numbers, email and web portals to help speed business transactions. We are very rapidly approaching a frontier where both employees and customers will demand that businesses and institutions interact with them using mobile devices and special purpose apps. Failing to foresee and prepare for this is extraordinarily shortsighted, and could cost laggards dearly.

Managing Android in the Enterprise

December 7, 2011 in Uncategorized | Comments (0)

Tags: , , , , , , , ,

Android devices are coming on strong with consumers. In Q3, it claimed a remarkable 27% of tablet device sales worldwide, which is a stunning result, given that all of the buzz was in the iPad camp. Even more impressive, AT&T, original home of the iPhone, reportedly doubled its Android phone sales in the same quarter. Despite fears that Google would spook its partners by jumping into the Android hardware space, consumers seem to be beating a path to their collective doorways. Given this, it is worth getting ahead of the impacts of a likely population explosion of enterprise user supplied devices of the Android persuasion.

It is for this very reason that a recent article in Network World about Android’s potential issues for the enterprise mobile device management caught my eye. If you are responsible for managing mobile IT infrastructure, chances are you already appreciate that Android isn’t just one thing, or even a closely related series of individual things. Rather, it is a basic mobile OS framework upon which device vendors can build, allowing full customization and ample opportunities for the device vendor to differentiate and position products. A lot of popular, relatively low cost Android consumer devices are very light on security features. This stands to reason, because for most consumers, beyond a certain fairly fundamental level, security is just inconvenient. Device manufacturers would far rather build in features that attract customers

In terms of managing and securing Android device access to enterprise assets and infrastructure, relying on well hardened perimeters is probably going to be less successful and efficient than prioritizing and addressing critical threat scenarios. If I had to choose one threat scenario as a place to start fortifying Android device defenses, it would be creating strong privacy and security for mobile messaging streams. Here’s why:

Recently, I’ve been hearing more and more about a mobile hacking technique known as ‘spearphishing’. Unlike older phishing techniques which broadcast malware-laden spam in hopes of snaring the naïve, spearphishers use sophisticated mechanisms to steal personal information, accrete enough of it to concoct highly authentic looking bait, and then approach a specific target impersonating a highly trusted source. Some documented spearphishing incidents have achieved large scale, effectively infiltrating entire institutions’ IT infrastructure. Moreover, they can go undetected for long periods of time if their activities are not aimed at causing disruption, but instead at harvesting valuable data. Before a facing management of a significant crowd of weakly protected BYOD Android devices, have some built in precautions that keep enterprise messaging streams from becoming a playground for spearphishers.

Is BYOD spreading to the desktop?

November 8, 2011 in Uncategorized | Comments (0)

Tags: , , , , , , ,

We are on the show floor at SapphireNOW Madrid and there are many companies and mobile devices here for an exciting week. Many companies are moving toward a “bring your own device” (BYOD) approach to mobility management. There are a number of reasons for this. One is the fact that it’s happening anyway. Workers bring their own devices into the work place because they prefer using their own devices, and they work more efficiently on them. Another reason is that managed properly, BYOD can save companies money.

Many companies are finding that an enterprise grade device and application management platform simplifies the challenge of managing a diversity of mobile devices. These platforms are specifically designed to be mobile device agnostic. This gives companies greater flexibility in the mobile technologies they can use in their business operations. However it also raises an interesting question. Will a robust, device agnostic, application and device management platform create an IT infrastructure that offers more flexibility in the kinds of desktop devices workers can use?

A recent article in CNET reported on some interesting findings by a Forrester study. The article said this:
“Even though the vast majority of companies around the globe are still using Windows PCs, Macs are starting to find their way into offices–just not through the traditional means, a new study from Forrester Research has found.

According to the firm, 22 percent of the 590 enterprise IT executives Forrester surveyed say that they’re seeing an increase in the number of employees bringing their personal Macs into the office. Further inspection reveals that 3 percent of respondents saw Mac use jump by more than 20 percent in the last year, while 5 percent of respondents said that the increase was in the range of 10 percent to 20 percent. Forrester said 14 percent of respondents have seen Mac usage by employees increase by 5 percent to 10 percent.”

The article goes on to point out that many companies do not allow workers brining their own Macs into the office to have email access or run other business applications on them. However the Forrester study questions whether companies will stick to this policy over time. Given the advantages some companies find in supporting a BYOD mobile device environment, and given that companies are building infrastructures that support a diversity of devices, it’s worth asking if mobility is leading the way to an entirely different attitude in the enterprise about how to manage client systems.

Application Interoperability and the Mobile Enterprise

October 31, 2011 in Uncategorized | Comments (0)

Tags: , , , , ,

Recently I happened upon an interesting blog that was posted several months ago by a developer commenting on the use of specialized mobile apps. In his post, called The App Interoperability Conundrum, he makes the following observation about using his iPhone:

“It is without question that mobile devices will continue to proliferate in the consumer market with improvements in mobile infrastructure, device affordability and cultural acceptance. However I see an uneasy trend in mobile applications, that is, mobile applications are becoming increasingly focused but less interoperability.

To illustrate this point, consider the following hypothetical example. I am in downtown Los Angeles, I’m hungry and need nourishment from a reputable establishment. On my iPhone I can use:
1. Google Maps to find a nearby restaurant,
2. MapQuest to get voice guided routing directions,
3. Built-in camera to record my memorable meal,
4. FourSquare to “check-in” and recommend this restaurant to my friends, and
5. Yelp to post a review (and snapshot) of my dining experience.

In this workflow, the only interoperable elements were the street address I copied from (1) to (2) and the photo created in (3) and shared with (5).

Obviously this workflow could be optimized by using one app to perform two or more tasks like using Google Map to a find a restaurant and driving directions. But these five apps, in my hypothetical opinion, were the best in each task.

My criticism is not targeted at the number of app used during my lunch break but the lack of interoperability between them. For example:
1. From Google Map, why is it not possible to send the restaurant address directly to my favorite routing apps?
2. From the camera app, why is it not possible to share a photo directly with Yelp.
3. From MapQuest, can I send the “route” to my friends so that they know where I am driving from?
4. To rate (or “check-in” at) the restaurant with FourSquare and Yelp why did I have to locate the restaurant in each app?

Why not just click the “get current establishment” button in each app?

These comments may seem like iPhone-bashing, but they are not. I am just bringing your attention the unintentional ‘stovepiping’ caused by increasingly focused mobile apps.”
For a consumer, this lack of interoperability between applications is an inconvenience. However when it comes to enterprise mobility, the interoperability conundrum can become a serious impediment to efficient business operations. People make decisions based on the information that is available to them. Sales data informs business planning. Marketing and sales information combined with supply chain data impacts production. An intelligent organization’s operations depend on shared information.

That ability to collaborate and share information in real time is a major reason why mobility has become essential to business operations. Yet what happens if mobility is pursued in a non-strategic way? What happens if every work group adopts its own mobile applications without regard to other operational dependencies? The result will be “stovepiping” of business operations caused by a lack of application interoperability.

As you build a mobility strategy, it is critically important that you do so in a way that enables application interoperability. You may not know how tomorrow’s applications will depend on today’s or yesterday’s data, but you need to have a mobility infrastructure that gives you the flexibility to share information between applications. This is what a mobile application platform like Sybase Unwired Platform does.

Thieves Love Smartphones

September 29, 2011 in Uncategorized | Comments (0)

Tags: , , , , , ,

Law enforcement calls it “Apple picking”. It’s really just a new kind of snatch and dash, but smartphone thievery boosted overall year-over-year theft statistics for the Chicago Transit Authority by 23% in June 2011. And it’s not just happening in Chicago. Many other urban centers are on the same trend line.

In New York City, transit police are currently conducting undercover operations to discourage device theft on the subways. The plain clothes officers travel the rails, with up to 200 undercover police patrolling at any given time. The NYPD knows the score. Pickpockets love smartphones. In London, the transit authority has issued this warning to tube riders. “Treat your iPhone like a 100 pound note, because that is what a thief sees when you use it in public.” Over the last year there, thieves have become increasingly brazen. Daylight robberies have become routine, where devices are snatched right out of callers’ hands, even while conversations are in progress.

This sort of crime is a triple threat to mobile business workers. First, it deprives them of tools, data, and communications necessary to do their work; second, it must be assumed that whether the theft was targeted or not, the business data on the phone may be subject compromised; and third, these devices are not cheap.

Companies need to be prepared for device theft and loss because it’s going to happen. Here are some things you can do:

· Data encryption should be routine for all business data that resides on the phone for any amount of time. If workers keep sensitive personal data on the phone as well, things like personal identification information, credit card and bank account numbers, passwords, or any other kind of sensitive information, they would be wise to encrypt all this data. Businesses can and should mandate this for their workers. Of course they will need a security management platform and consistent security policies and practices to enforce it.

· Access to all business functions should be password protected.

· Maintain 24/7 availability of mobile application management facilities for remote device wipe and remote lockdown. Employees need to be encouraged to contact a company hot line right away if they suspect their phone is lost or stolen. Reward them for this action. Delays can be costly. Companies should also have rules for automatic data fading in place in case a user does not know right away that their phone has been stolen.

· Particularly in a “bring your own device” (BYOD) company, workers should be encouraged to get theft insurance, to be aware of its provisions for device replacement, and to carry contact information for the insurer in a place that is separate from both phone and wallet.

· Several carriers and phone vendors provide services for tracking stolen devices. Again, device users should carry contact information for these services in a place separate from wallet and phone. To have a chance of locating a device, it is very important to contact the locator service as quickly as possible. Thieves may be savvy enough to ditch the SIM card.

Educate mobile business users about the risks of losing a device and best practices for keeping data secure. It helps to have a “culture of security” in which the company has clear security policies, a platform the enables and enforces best practices, and users who know what to do if the worst happens.

Top 2 Hybrid App Management Scenarios

September 15, 2011 in Uncategorized | Comments (0)

Tags: , , , , , , , , , ,

Continuing the Hybrid container application development conversation, let’s consider application management. Hybrid applications are also easier to install on workers phones. Consider these application management scenarios:

First, let us say your company has developed a mobile travel approval application you want all employees to use. This application will streamline and accelerate travel approvals, enabling travelers to make arrangements earlier and reduce their spending on last-minute bookings. Your company permits users to bring their own phones to work, though you limit them to a list of approved devices that covers four different mobile operating systems.

The native application approach would be to build four versions of this application – one for each supported mobile operating system. When it comes time to deploy the application, it is necessary to interrogate each device to see which operating system it is running, and then install the appropriate version of the travel approval app.

Using a hybrid application strategy, you would build the travel approval application once. It would be the same for all devices. When it is time to deploy the application, you would provision it over the air to all company employees and it would immediately become a functioning app on their devices.

Note that company enabled devices would already have containers installed. This would likely happen when the phone was initially enabled for business use. For instance part of the “business enablement” process might include installing a basic company app like email or a company directory. That app would include a device specific container. Once the container is installed, that device will run other company developed hybrid apps that are installed over the air by IT management or downloaded from the company app store.

Second, let’s say your company has set up an app store where employees can download business applications. The process for downloading a hybrid application would be simpler.

When workers go to the app store to download a native app, they will encounter a step requiring them to indicate the type of device they are using, or to select the device specific version of the application they are looking for. Once the application installs, they may need to do some device specific configuration. If they select the wrong download, the application will not work.
With a hybrid application on the other hand, workers would simply go to the app store and select the application they want. The application will download and run every time.

Using container dependent hybrid applications makes it easier to segregate business and personal use functions on a dual-use device. That is a valuable capability at a time when employees are increasingly bringing their own devices into the work place.
Hybrid applications also provide an inherent layer of security. The hybrid applications only work in a compatible container. If by chance someone had access to the web app component of a hybrid app from our company, unless their mobile device was enabled for use in your company and had a device specific container installed on it, the web app component would not function.

There is great business value in simplifying mobile application deployments. To get the most out of a hybrid application strategy, applications should be built on a mobile application development platform that enables you to easily customize containers for the devices and data sources your organization uses. That way you not only have containers that are custom fitted to your operational environment, but you can create a standard container architecture that makes hybrid apps easy to build and deploy. Hybrid applications are also easier to update so that you can quickly change or adjust software driven business operations.

In this kind of mobile business environment, workers see new functions and applications appear on their devices, ready to run. Also, the task of worker initiated downloads and configuring a new application becomes much easier. This reduces the load on tech support, and it increases the adoption rate of new applications designed to make business operations more efficient and workers more productive.

Simplifying Mobile App Provisioning with Hybrid Applications

September 8, 2011 in Uncategorized | Comments (0)

Tags: , , , , , , , , , , ,

The days when mobile email was the app and a BlackBerry was the device are long gone. A mobility revolution has brought a world of new device types and applications into the workplace. Workers now take for granted mobile capabilities that were totally unavailable to them just a few years ago.

This new age of business mobility has presented challenges for companies whose workers rely on mobility to do their jobs. For one thing, there’s a much greater variety of smartphones and other devices like tablets in the workplace. Even as companies are realizing the value of allowing their workers to bring their own devices to work, and as they develop policies to secure company data in this kind of environment, they are faced with an even greater challenge: managing a rapidly growing portfolio of mobile applications.

There was a time when the cost of building mobile applications for enterprise-wide use limited their development and deployment. However that is changing. Workers are downloading low cost applications for their own use. Independent software vendors are marketing high functionality mobile business applications. Companies are deploying mobile application platforms that significantly lower the cost of building, their own portfolios of proprietary mobile apps.

Amidst this proliferation of mobile applications and devices, companies are wrestling with the various versions of applications they must create to support they different devices allow at work. They are exploring ways to more efficiently manage and deploy growing numbers of mobile applications. Many companies are adopting an application management platform that supports the “company app store” model as well as other capabilities like dynamic device interrogation, which provides visibility into devices being used in the business.

There is a new approach to mobile application development that is likely to cause an even greater proliferation in the numbers of business applications. This is the use of hybrid web applications for business mobility. Hybrid application cost less to build while providing the same performance capability as native apps, and in many ways, they are easier to manage.

Hybrid applications are web apps running inside native application containers that are installed on mobile devices.

The native application containers are specific to device types. This means they are able to access and control all the device specific features like memory, camera and GPS, and other features in the same way a native application would that is designed just for that device and mobile operating system. Containers can also be set up to access back-end data stored in server or cloud based corporate databases.

The hybrid application’s business logic is built into a generic web app using HTML5 and JavaScript. Being a web app, this application is the same for all devices. When it is accessed through a mobile device’s browser, it runs in the container installed on that device. The container executes the hybrid app’s functions as if it were a native app built specifically for that device.

One great advantage of this approach to building mobile applications is that it lowers the cost of application development. Instead of creating different versions of every application to support all the different device types that need to run it, the application is built once. It will then install and run on any company device that is enabled, with a container, for business use. This is one advantage, and as always there is more to come.

How Hybrid Apps Simplify App Development and Maintenance

September 1, 2011 in Uncategorized | Comments (0)

Tags: , , , , , , , , ,

As promised here is more to think about and apply to the cost of building and maintaining mobile apps!
There has been a lot of interest recently in building browser based web applications as mobile business apps. This approach would greatly simplify mobile application development. Any smartphone or tablet that can browse the internet would be able to run a web app. This means it would only be necessary to build and maintain one version of these applications.

Although this approach works for simple applications, mobile applications built this way have a number of limitations, including:
• Web applications have no direct access to device specific hardware. This limits theretheir ability to use device specific features like cameras and GPS, and it also gives developers less control over how data is handled on the devices, which could lead to security issues. Also, web applications have limited ability to process large data volumes.
• Web applications do not provide any control over which devices are connecting to the enterprise’s web server.
• With web applications, end users must self-provision apps & bookmark links. It is not possible to send one app to all device users at one time. It is also not possible to use push messaging to distribute notifications and content to employees.
• It is not possible to customize the look and feel of HTML web pages for different devices; each page needs to be changed individually for this to occur.
• Web applications are slower than native apps, which makes it more difficult to give the “on device” application user experience.

There is, however, a different approach to web applications which gives them all the performance advantages of native apps while retaining the development and maintenance advantages of web applications. This involves the use of a native app “container” which becomes the environment in which a web app runs on the mobile device. These are called hybrid applications.

A web app container is a native application designed to process generic function calls from a web application. The container itself has device specific hardware controls and hooks to back end corporate databases. Each mobile device type supported by the company would have its own version of a container, which would be installed on the device when it is enabled for business use. Web apps operate within the containers so that the same generic function calls would work appropriately on the different mobile devices. For instance a web app that called for a GPS function would work the same on an Android, iPhone, or Blackberry once those devices had containers installed on them.

Hybrid applications offer a tremendous opportunity to lower the cost of mobile application development and maintenance. This is another piece of the cost of mobile apps conversation. There is more to come.