Pages

Showing posts with label policies. Show all posts
Showing posts with label policies. Show all posts

Sep 21, 2012

Study: In the Enterprise, Tablets Without Training Can Mean Anything But Sales

Study: In the Enterprise, Tablets Without Training Can Mean Anything But Sales As an increasing number of tablets make their way into the enterprise, and as companies scramble to establish BYOD policies, there remains an important question:  is anyone making an effort to train the users about the proper use of their devices? The folks at the SAVO Group were also curious about this.

Tablets - Training = Angry Birds (and Bosses)

SAVO Group cites a study conducted by the Sales Management Association (SMA), "Mobility: Where Your Sales Force is Heading (With or Without You)". The study found that among the 26 percent of participants who reported their organizations are providing tablets for sales representatives and the 43 percent who said their organization supported the Bring Your Own Device (BYOD) trend, an overwhelming 67 percent are not being trained on best practices for utilizing the tablet during customer interaction.

The study also revealed that respondents were using tablets for communication, web access and social media applications rather than customer presentations or CRM applications. In the absence of formal training and policies, tablets are quickly becoming a costly investment in email, social networking — and no doubt, Angry Bird tournaments — for sales representatives.

Adopt an Effective Tablet Strategy

What can you do to ensure that some enterprise tablet users don’t disrupt your organization? SAVO Group recommends having a clear adoption strategy, prior to deployment, noting that it should include training those who will using tablets for specific purposes related to sales, inventory or customer service. Not only will this serve to increase adoption, but ultimately, it can also help to drive revenue growth.

Organizations should also consider aligning their applications with a sales process and distributing well-defined usage goals. This is particularly important as 77 percent of those surveyed mentioned their desire to include sales process integration with their iPad adoption. Participants also weighed in on the types of tablet applications that would make them valuable for sales representatives. Most often mentioned were apps that included:

  • Access to approved corporate materials (74 percent)
  • Virtual white boarding (74 percent)
  • Multimedia applications (69 percent)
  • Webcast hosting (63 percent)

While there is a strong feeling in the industry that tablets won't be replacing laptops anytime soon, it's clear that they can play a role in the enterprise — provided they don’t compromise your security or complicate tasks. But like any emerging technology, it’s important to educate and promote awareness about how to use it so that it becomes an empowering tool — not a disruptive one.

 
 

Source : cmswire[dot]com

Sep 6, 2012

Twitter Gets Strict with Official API v1.1 Release

Thumbnail image for Thumbnail image for Thumbnail image for official-twitter-bird-white-on-blue.pngTwitter has officially released version 1.1 of its API. Initially announced in August, the updated API has stricter authentication policies and developer rules of the road, among other new features.

Twitter Toughens Up

In version 1.1, Twitter is requiring applications to authenticate all of their requests with the API. Twitter says this step will prevent abusive behavior and help it to further understand how categories of applications are using the API so it can better meet the needs of developers.

At this time, all authentication requires user context, but in the coming weeks Twitter says it will release support for a form of authentication not requiring a user context.

Twitter also updated its developer rules of the road, placing regulations against activities such as publishing private user information, resyndicating data and performing “surprise” actions not initiated by users. And all applications replicating the core Twitter experience, usually called "clients," will have some new restrictions placed on them, including a 100,000 user token limit.

There are also new display requirements (which were previously suggested guidelines), dictating things like display of the tweet author avatar and how text is displayed. Other changes include support for JSON only, discontinuing support for XML, Atom and RSS, which Twitter says are “infrequently” used.

Rate limits in version 1.1 of the API are divided into 15 minute intervals, which is a change from the 60 minute blocks in version 1.0. Additionally, all 1.1 endpoints require authentication, so no longer will there be a concept of unauthenticated calls and rate limits. Search will be rate limited at 180 queries per 15 minute window for the time being, but Twitter says it may adjust that over time. According to Twitter, developers will “now be able to query the API on a per endpoint basis a lot more than (they) previously could.” 

Show Me the Money

Although Twitter is stressing that the new changes will help eliminate abuses and make Twitter app development a more structured and orderly process, not all observers are convinced its motives are entirely pure. Last month, CMSWire columnist Stephen Fishman wrote that,

Twitter really does not care whether (solo developers) make money. Twitter cares whether Twitter makes money. In order for Twitter to make money, Twitter needs consumers to engage with Twitter on the Twitter site as much as possible. Twitter's value prop to developers is a free, functional and highly available micro-bloging platform that can easily be integrated into your site.”

Fishman also said the new API is directly aimed at “data scrapers” whose primary goal is to extract Twitter data for their own benefit.

Resyndication Rules Could Cause Problems

According to Mashabale Tech, new restrictions on resyndicating data appear to mean that information contained within a tweet — such as a URL — cannot be sent to another service using a third-party client. Mashable says this “could be problematic for social news aggregators such as paper.li, Postano and RebelMouse” and “have a much larger impact on the entire Twitter ecosystem,” including mainstream applications as well as third-party developers and power users.

Ultimately, Twitter is probably in a position to enact whatever API rules it likes and ride out any developer backlash. As Fishman states in his article, “If (Twitter’s value proposition) is not good enough, build and market your own platform and see how much money that makes you.”

 
 

Source : cmswire[dot]com