Having business applications available while away from the office is nothing new; neither is using mobile devices as an integral part of a business process. Until recently, however, the former has mostly consisted of standard PC applications running on a laptop, and the latter has largely been the realm of specialist, often ruggedized mobile devices used for a single purpose, such as delivery tracking or stock-taking. The advent of smartphones and tablets has changed the dynamics of what mobility means in a business context.
One driver clearly has been the desire of business professionals to stay in touch and keep workflows moving even when not at their desk: 58% of information workers use a smartphone and 30% use a tablet for work (either employer-provided or personal). Even more importantly, the executives holding the purse strings have discovered the power of mobile. Not that tablet-toting business leaders are anything new; the “cool factor” of the iPad in particular meant that it quickly became a status symbol. But there’s been a more subtle revolution behind the scenes: once early adopters had started moving towards the electronic distribution of board papers, board members themselves started spreading the message, challenging organizations that were still paper-bound to go digital.
Salesforce1 was the big development revealed at salesforce.com's huge Dreamforce 2013 conference. But many left the conference wondering the same thing: What exactly is Salesforce1? A new mobile app? New sales, service, and marketing applications? A new set of application programming interfaces (APIs)? New development tools? Our analysis gets under the hood of the announcement, finding that Salesforce1 is “all of the above” and a big step forward for the company, cementing its position as a top choice among public cloud development platforms.
Salesforce1 consolidates and modernizes salesforce.com's mobile client efforts into a single extensible app. There's a gap in offline work still to be fixed.
The Salesforce1 mobile app required a major refactoring and expansion of salesforce.com's APIs. Developers now have a much wider range of functions available to work with salesforce.com's various Web properties. The new APIs are RESTful.
The new APIs opened the door for much better integration between Heroku and salesforce.com's Web properties. Heroku is the company's environment for Ruby, Java, and other developers who don't or won't work in Force.com. Now both development environments are integrated with salesforce.com's applications and underlying application services.
Salesforce1 is a big set of developments, and addresses one of our biggest criticisms of the company's cloud platforms: that Force.com, Heroku, Chatter, and other services aren't well integrated. Well, now they are.
Business decision-makers in Asia Pacific (AP) are increasingly aware of the importance of business intelligence (BI) and broader analytics to business strategy and execution. However, lack of internal expertise remains a significant barrier to BI project success.
To succeed in the region, BI service providers must provide guidance on how to translate data access into actual insight and information into business value. This requires a strong understanding of local cultures, business practices, regulatory frameworks, and market dynamics. When evaluating providers, understand how their capabilities are likely to evolve across five categories:
People. To minimize project risks, understand who will be the on-site business and technical leads on BI projects and how many successful implementations this staff has led in a similar industry and similar technical environment within the region.
Technical expertise. Service providers need to demonstrate region-specific knowledge of the technical characteristics of various BI tools, platforms, architectures, and applications. Most companies will not have all of the necessary skills on site, so closely evaluate ease of access to remote staff from the service provider as well.
“We’re in charge of developing your new website. You can have it good, fast, or cheap. Pick two.”
How many times have you heard (or said) something like that on a digital experience project? With any digital initiative, one of those desires is usually odd man out. Application development and delivery pros at corporations, digital agencies, and systems integrators know this; they’re often the people talking reality in the face of the wishes of the business asking for all three (and, frequently, a fourth: “Can you make it as good as Apple.com?”).
Web projects always require compromise. The challenge is figuring out what you can live without.
It’s enlightening to apply the good/fast/cheap triangle to the Healthcare.gov snafu that’s been playing out in Washington, DC. If you’re involved in web applications, reviewing the government’s project might be one way to inoculate yourself and your team against an invitation to the hot seat by preventing website crash and burn. No one wants to be like the Secretary of Health and Human Services, Kathleen Sebelius, and her squad, who’ve had to explain the most visible website flop in history.
It makes me ask: how did the Feds deal with the good/fast/cheap question for Healthcare.gov? It’s a hard reality to deal with on any digital project, never mind a project of this scale. Where would you compromise?
In-line editing? Check. Personalization? Check. Testing and optimization? Check. As the web content management market matures, functional differentiators have become tougher to find. One of the remaining functional gaps in the market is a digital customer experience platform that supports complex but unified commerce-based and marketing-based experiences. Currently, these experiences tend to be disconnected due to technical (and organizational) silos.
Count Sitecore among the vendors — such as Oracle and IBM — hoping that a hybrid commerce and content platform will make an impact on the marketplace. This week, Sitecore acquired commerceserver.net. This marks the first marriage of significant .NET content and commerce (the other commerce/content combinations available — Oracle and IBM — are built on Java).
Good move? It is significant that another vendor has taken the step towards building a digital customer experience platform that includes both commerce and content offerings. And that’s where the challenge will come in. Both IBM and Oracle have faced the challenge of integrating commerce and content products that weren’t designed and built on the same architecture. Sitecore’s challenge won’t be any different. Time will tell if the whole is greater than the sum of its parts.
Forrester attended Microsoft’s second annual Asia Pacific Analyst Summit in Singapore last week for an update on the company’s progress in transforming into a devices and services company. The event highlighted Microsoft’s strengths and exposed some obvious challenges, which I’ve shared below. Forrester clients can access further event-related analysis and implications here.
Day One: Impressive Capabilities And A Strong Understanding Of Customer Needs
Day one was well designed and delivered, with a clear focus on customer and partner case studies and go-to-market strategies based on three core imperatives:
Transforming IT. Focusing primarily on Cloud OS, Windows Azure, and Office 365, this imperative highlights Microsoft-enabled capabilities and resources to help IT organizations transform both internal data centers and IT delivery.
Engaging customers and employees. This imperative essentially combines mobility and social to help organizations thrive in the age of the customer by delivering improved customer service and customer and user experiences.
Accelerating customer insight and business process improvement. This imperative targets the changing needs and expectations for data and information access and real-time decision making via a combination of traditional analytics and big data.
After a couple less-than-home-runs in the cloud game, it looks like CenturyLink might just have a real contender. The US midwestern telecommunications leader pulled the trigger on yet another acquisition this morning - Tier 3, a legitimate cloud platform provider. The real question is whether this is the latest in a long string of acquisitions that have failed to hit the mark, or a sign that they finally got it right.
CenturyLink is a Lego company built through a string of acquisitions all bolted together. It rolled up several telecom players to get to its current size and presence in that market. And it has bought now three cloud companies.
You take the blue pill, the story ends, you wake up in your bed and believe whatever you want to believe. You take the red pill, you stay in Wonderland, and I show you how deep the rabbit hole goes. — Morpheus, The Matrix
Mobile development, like Morpheus in The Matrix, offers two options: Take the blue pill and assume that mobile is just another screen size to front ends that we’ve already created. Take the red (with me) and understand that mobile changes not just the front end, but your entire technology stack! Ready to look down the rabbit hole?
A new supply/demand paradigm is driving enterprise architects and application development professionals to a technology inflection point. The demand is for mobile apps — consumers have an insatiable appetite for more apps, developed and updated at breakneck speeds that deliver mind-blowing experiences. And the mobile app consumers aren’t just external — they’re also employees and business partners. As app-dev pros, where do we turn to supply this growing demand? Application programming interfaces, better known as APIs.
Before we get into details of this challenge in the real world, I’ll promote my four-tier architecture that looks at this API layer within the entire technology stack used to support your mobile efforts. You’ll find it in my report Mobile Needs A Four-Tier Engagement Platform.