Is Apple’s dispute with Microsoft over Skydrive for IOS forcing Microsoft to focus more on HTML5?

SkyDrive

Last month, we heard that the cause of the delay to updates to a number of Microsoft applications (like SkyDrive and SkyDrive Pro) on the IOS App Store was a dispute between Apple and Microsoft over Apple’s insistence that all app developers who monetize their Apps that have been downloaded from the Apple App Store pay Apple a 30% royalty fee.

For those developers who post free apps to the App Store, they have nothing to worry about.  However, Apple is now starting to hone in on those developers that use the App Store as a free channel to market by publishing ‘free’ apps that later require the user to pay a fee or licence to the developer.  Apple says that these in-app fees and purchases should be subject to the same 30% royalty payment as Apps that are paid for directly in the App Store marketplace.

This is a big problem for Microsoft and other App developers because Apple’s terms and conditions, which Apple states are uniform for all developers, require the developer to pay Apple a 30% margin on all in-app purchases, upgrades, enhancements, etc. – in perpituity; even if the end user switches to another mobile platform in the future.

Microsoft has found this condition quite hard to digest as you might imagine and now finds itself in a state of limbo as far as its portfolio of IOS apps are concerned.  For instance, the IOS SkyDrive app has a new version ready to be deployed with important feature and security updates, but it has not been published to the IOS App Store yet.

Enter HTML5 Apps
Coincidentally, Microsoft recently announced major new enhancements to its HTML5 version of SkyDrive, supporting swiping gestures and drag and drop features that many would only think possible with native device applications.

So, has Microsoft begun the process of by-passing native application App Stores to focus on rich cross-platform HTML5 mobile web applications?  In reality, the answer in the short term is probably not, but they are certainly pursuing a multi-channel mobile strategy that will make the HTML5 option more attractive in the future, particularly if it means having to avoid costly fees to App Store operators.

In the enterprise space however, we see HTML5 applications having a much more powerful impact.  HTML5 mobile applications are the only true way for a CIO to implement an all-inclusive BYOD or cross-platform mobile strategy economically and they do not require costly investments in Mobile Device Management (MDM) infrastructures.

Check out www.azurati.com to see how HTML5-based mobile applications are being used in the enterprise to transform the productivity of mobile business users.

 

Advertisements

Nielson Norman announce 10 best Intranets; mobile still lagging behind

Nielson Norman Group, a leading Intranet design and consulting firm, have just published their annual top 10 Intranets study; an annual review of the top 10 corporate intranet sites from companies around the world.

Nielsen Norman’s top 10 best designed intranets for 2013 are:

1. Acorda Therapeutics, Inc. Biotechnology USA
2. American International Group, Inc. Insurance USA
3. AT&T Telecommunications USA
4. Hager Group Manufacturing Germany
5. Luzerner Kantonalbank AG Financial Services Switzerland
6. ONO Telecommunications Spain
7. Saudi Commission for Tourism and Antiquities (SCTA) Governmental Agency Saudi Arabia
8. Swiss Mobiliar Insurance and Pensions Insurance Switzerland
9. WorkSafeBC Workers Compensation Board of British Columbia Canada
10. XL Group Plc Insurance Ireland

Interesting points to note from the report are that, according to Nielsen Norman, over 70% of corporate intranets are built on a Microsoft SharePoint platform, and mainly due to the fact that corporate intranets take a very long time to develop and perfect (an average of 26.5 months or 2.3 years), mobile enablement of corporate intranets is seriously lagging behind other new features, like Social Collaboration.

This means that many corporate intranets are failing to address the needs of a growing number of users who want to be able to access corporate information and knowledge on mobile devices.  Gartner estimates that by the end of 2014, 70% of enterprises will have implemented a BYOD strategy and the corporate intranet is one of the most obvious enterprise resources that should be made available on mobile devices.

The report lists common mobile barriers as being:

  • Security concerns
  • Difficulty of choosing a platform
  • Lack of resources to create and maintain mobile builds
  • Uncertainty about whether to implement a full feature set with a good mobile user experience or an app for particular tasks

Creating mobile SharePoint intranets
As with all things software, there will always be the debate as to whether one should build and develop a bespoke solution, or whether a commercial off-the-shelf solution would make better commercial sense. The same will undoubtedly be the same when you come around to considering mobile-enabling your SharePoint-based intranet.

Azurati SharePoint2Go_compared_with Standard_SharePoint

Our (biased) counsel, would be to refrain from custom development of mobile interfaces with SharePoint.  It is a fairly well known issue that Microsoft has not done a good job with the standard mobile templates that ship with SharePoint.  Even with SharePoint 2013, developers are dissuaded from branding and customising the standard mobile templates that ship with SharePoint.  In addition, new mobile templates need to be developed for each form-factor that is released, which can lead to prohibitive on-going costs of maintenance and support.  That is why solutions like Azurati’s SharePoint2Go solution is able to deliver mobile enabled SharePoint that will work seamlessly on any mobile device in five minutes.

Not only does SharePoint2Go deliver an instant cross-platform mobile solution for SharePoint intranets, it also includes over 15 options to authenticate your mobile users securely; with everything from forms-based authentication to 2-factor built in to SharePoint2Go’s administrator wizards.

SharePoint2Go your way
If your SharePoint intranet is heavily customised with value-adding functions that make your desktop version of your intranet a productive experience (like company news, people finders, document repositories, management dashboards, etc.), SharePoint2Go can be extended by developers to create mobile versions of custom SharePoint web parts – we call them V-Parts.  V-Parts can be designed to be used within the mobile SharePoint interface, or as stand-alone full-screen mobile applications that can operate in offline mode as well as online.

As an HTML5 mobile application that is accessible via the mobile device’s browser, SharePoint2Go will work with feature-parity on any mobile device, no matter what the market throws at you; making it the ideal solution to complement your enterprise mobile or BYOD strategy.

Find out more
If you are looking to mobile-enable your SharePoint intranet and you are looking for a solution that:

  • is built with enterprise security in mind
  • will work on any mobile device or form factor, with feature-parity, and will therefore complement your enterprise mobile or BYOD strategy
  • will not require costly internal development teams to develop and maintain your mobile environment, or costly Mobile Device Management (MDM) solutions, get in touch with Azurati.

To find out more about Azurati’s SharePoint2Go solution for mobile-enabling Microsoft SharePoint and to request a free 14 day trial, contact info@azurati.com or visit www.azurati.com.

New year; new enhancements for Azurati’s enterprise mobility solutions

The development team at Azurati would even have impressed Santa’s Elves this Holiday season with the raft of new exciting innovations and enhancements that they have managed to roll-out to support our secure, cross-platform mobile enterprise proposition.

Today, we are excited to announce a number of new innovations that have not previously been available to any enterprise mobile users, which we hope will boost the adoption of HTML5-based mobile applications in the enterprise:

Azurati Mobile Portal
The Azurati Mobile Portal provides a new way for enterprise users to access HTML5-based mobile applications securely from any mobile device.  With the Azurati Mobile Portal, enterprise users are able to authenticate themselves once and then use the Mobile Portal interface as an HTML5 mobile application launchpad, enabling mobile apps to be launched with secure single sign-on.

Azurati Mobile Portal for HTML5 mobile applications

The Azurati Mobile Portal is great for both IT and the mobile user community because it provides a secure environment to access HTML5 mobile applications that can be centrally controlled (without needing expensive Mobile Device Management solutions).

HTML5 mobile applications are published to the Azurati Mobile Portal via the Azurati ASAP mobile application platform.

Azurati Apps
Azurati Apps are HTML5 applications that can be developed as cross-platform mobile applications from the ground-up, or as cross-platform mobile versions of existing enterprise software applications.

What’s more, for the first time, Microsoft SharePoint users who frequently access custom developed Web Parts in SharePoint, can create specific full-screen mobile applications from Web Parts that can be accessed via the Azurati Mobile Portal.  Examples of these may be Staff Contact lists, Product data lists, Company news and discussions, etc.

Azurati Apps

Azurati Apps can be developed to support Dynamic Offline access so that mobile users can continue to work and be productive even when Internet connectivity is lost.

Enhancements to Azurati V-Parts in SharePoint2Go
Azurati has made a number of enhancements to our V-Part architecture that now makes it easier than ever to convert custom developed SharePoint Web Parts and access them via Azurati’s cross-platform mobile SharePoint solution, SharePoint2Go.

If you find that the true value in SharePoint is not in its out-of-the-box feature set, but in the custom developed Web Parts and SharePoint apps (like Staff contact lists, project task lists, company news, BI reports, sales pipeline data, etc.), then for the first time, you will be able to continue to use these functions

Live editing of documents from SharePoint2Go
A common request from Azurati customers was the ability to edit documents from SharePoint2Go.  Up until now, this has been technically complex because of the fact that SharePoint2Go is a mobile web application.  However, we are pleased to announce a new capability that will allow live editing of documents from SharePoint2Go using Microsoft Office Web Apps on iPads.

The following screenshots show how this works (click images to view enlarged view):

1. Select document from library

Azurati doc live edit 1

2. Select Edit Document

Azurati doc live edit 2

3. Edit document in Microsoft Web Apps (this requires a valid user licence for Office Web Apps)

Azurati doc live edit 4 4. Save document

azurati doc live edit 5 5. Document edits are saved back to SharePoint2Go

azurati doc live edit 6

SharePoint2Go On-Premise deployments
We are pleased to announce also, that we are now able to offer On-Premise deployments of SharePoint2Go in addition to our standard Microsoft Azure Cloud option.  Enterprise customers who feel that they are unable to make use of Cloud-based services may install the Azurati SharePoint2Go server on internal servers behind the corporate firewall.

More information about Azurati
If you are considering HTML5-based mobile applications as part of your enterprise mobility strategy or if you would like to understand more about any of these announcements and Azurati’s HTML5 enterprise mobility solutions, please contact us via www.azurati.com.

So, was Facebook wrong about HTML5?

When Mark Zuckerberg publicly dumped HTML5 earlier in 2012, saying that ‘it was not ready’, many in the mobile applications development community sighed in disappointment and frustration; including the folks at Sencha, a mobile development platform provider for HTML5 developers.

So, Sencha decided to prove Facebook wrong by building their own replica HTML5 mobile web version of Facebook, called Fastbook that goes to show that it was not HTML5 per se that had previously caused Facebook’s mobile app speed and response times, but probably more to do with how Facebook had originally used HTML5 in their generation 1 mobile application.

fastbook-hero

“When a team has problems with HTML5, it usually stems from the fact that they take a “website” development approach to building an app, and often don’t use the right tools and architectures for application development. This is what we suspected about the Facebook HTML5 app”, says Jamie Avins of Sencha.

Fastbook is accessed via the mobile device’s browser and is truly impressive.  IOS users can save an application icon/badge to their iPhone/iPad homescreen, so it appears just like other native mobile applications.  It is fast and includes all of the key features of the original Facebook mobile application, but now instantly accessible on all mobile devices and platforms.

Try it for yourself by going to http://fb.html5isready.com/ on your mobile device.

FastBook is a great Showcase of the capabilities of HTML5, showing that you can develop fast, feature-rich mobile applications that will work on a single code-base across different mobile platforms.

HTML5 mobile applications in the enterprise
In the enterprise space, Azurati has been promoting the adoption of HTML5 mobile web applications for some time.  HTML5 applications should be considered by CIOs as a viable alternative to native mobile applications, for certain types of enterprise mobile applications.  For a start, mobile web applications do not require expensive Mobile Device Management (MDM) infrastructures.

However HTML5 web applications that require user authentication in the enterprise space suffer from a common issue and that is that the user either needs to bookmark the mobile app (like a website), or the user needs to remember the URL of the mobile app – if using a non-IOS device.  Azurati has come up with a unique solution to this that we call the Azurati Mobile Portal.

Azurati Mobile Portal for HTML5 mobile applications

Azurati users are able to access enterprise HTML5 mobile web applications securely and conveniently from a single mobile portal interface.  Users authenticate themselves once and can then open verified mobile applications from the Mobile Portal with Single Sign-On, providing a more secure solution for IT and a better user experience for the end user.

For further information on how to use development tools like Sencha Touch to publish HTML5 applications to the Azurati Mobile Portal, visit www.Azurati.com.

How inclusive is your BYOD policy?

When companies say that they are going to implement a Bring your own device (BYOD) policy, allowing employees to use their own personal devices (smartphones, tables and even laptops in some cases); what do they actually mean?

What exactly is covered in your BYOD policy, and what is not?  For instance, do you say that you support BYOD, but then exclude certain devices; and what do you expect your staff to be doing on their personal devices when they are using them for work purposes?

Sometimes it can be seen to be an easy and logical decision to declare an all-out Bring Your Own Device policy.  After all, your staff will undoubtedly thank you for allowing them to use their (usually) newer and higher-spec devices and your Finance department will laud your capital expenditure cost-cutting prowess; but if you suspect that your users will want to use their smartphones and tablets for more than checking email and making voice calls (on phones), then there are clearly a raft of additional factors to consider.

Let’s take these points one by one.

What do you mean by BYOD?
If BYOD means for you that an employee can bring any personal device in to the workplace and use it for business purposes, then great.  However, that is not the interpretation that many companies actually have.  What they really mean is you can bring your iPhone/iPad, and Android device, and possibly a Blackberry device; but probably not devices like Microsoft Surface RT tablets, Windows Phone devices, Google Chromebooks, Amazon Kindle Fire HD tablets, Apple MacBooks, etc.?  The truth is that many BYOD regimes are not all-inclusive and companies are compelled to exclude certain devices because enterprise mobile strategies are not always aligned with BYOD policies, meaning that mobile apps and management infrastructures are often not able to cope with BYOD.

Why should you not be able to allow any device in the workplace?  I hear you say.  These devices all use operating systems that support internet browsing and local applications and if you are embracing the concept of Consumerisation of IT, then it would be entirely logical to allow an employee to use their latest Christmas present gadget in the workplace.   A true BYOD policy should be all inclusive and IT should allow users to bring any connected device in to the workplace and expect to be able to work securely on it for work purposes.

For those of you who do want to embrace the principle of BYOD, but who are struggling with being able to execute an effective an non-restrictive policy, perhaps you should look more widely at your company’s goals and strategies for embracing mobile devices and solutions; which brings us on to the next point.

What will employees be expected to do with their personal device in a work context?
If you expect your staff to do more than use smartphones for voice calls and to pick up corporate email, then you will almost certainly want them to be able to work productively when working on a smartphone or tablet.  One of the on-going debates about mobile applications for enterprise users is whether BYOD also goes as far as Bring your own Apps.

There will undoubtedly be some apps, like Office productivity tools or web conferencing that make little impact on corporate IT security policies, but if mobile users need to have mobile access to secure enterprise systems, that is another issue.

Authentication and security are major issues to get a handle on if mobile users are expected to access corporate systems across the firewall.  So too is the state of readiness of corporate applications for mobile use.  Enterprise applications like Microsoft SharePoint, for instance, have woefully poor mobile user interfaces as standard.

Corporate IT departments need to think about how mobile users can gain secure access to enterprise systems, content and data

Should you consider a native application or HTML5 mobile app strategy?
This is one of those ‘how long is a piece of string’ questions and the answer will depend on the type of mobile enterprise application, who the intended users are likely to be and what devices they are likely to use.

As the table below shows, the best way to guarantee that your enterprise mobile applications will be compatible with your BYOD policy will be to implement mobile web applications; but in reality, native mobile applications will continue to be used for certain types of applications and target user groups:

Pros Cons
Native mobile Apps
  • Rich functionality
  • Offline access (for some apps)
  • Good for apps designed for individual users or work-groups
  • Difficult to deploy across the enterprise
  • Ensuring apps are correctly updated can cause governance issues
  • App developer may not support all mobile platforms, which may limit your ability to implement BYOD
  • Some apps may cache or save content and data on the mobile device, which should be reviewed alongside your mobile security policy
HTML5 Mobile Web Apps
  • True cross-platform mobile device compatibility
  • Feature-parity of app functionality across mobile platforms
  • Instant deployment of mobile apps and solutions to users
  • Updates for cloud-based services are applied instantly to all users
  • Potential for zero-footprint (no content or data left on the device)
  • New generation of HTML5 apps can support offline working
  • Good for mobile apps that will be used by large numbers of users
  • Users generally require an internet connection to use apps
  • Apps are accessed via the mobile device’s browser
  • Apps may not be able to take advantage of device functionality, although newer generation mobile web apps are able to do so
  • Speed and response times may be slower if accessing app over a poor connection

The newest generation of mobile web applications can behave just like native apps.  They are accessed via home screen application badges/icons and, although they are accessed via the mobile’s browser, they look and behave almost exactly like their native mobile app cousins, but with all of the advantages of being a web based application, like cross-platform compatibility, strong security, and the central purchasing, deployment and updating of licences; without having to necessitate an investment in costly Mobile Device Management (MDM) infrastructures.

How does Azurati support all-inclusive BYOD?
Being a leading HTML5 mobile enterprise application and mobile development platform vendor, Azurati fully supports and endorses all-inclusive BYOD programmes through its mobile enterprise applications and solutions:

1. SharePoint2Go® Secure cross-platform mobile Microsoft SharePoint, allowing mobile users to access SharePoint content, data and custom web parts on any mobile device
2. Azurati Mobile Portal™ Secure mobile container that acts as an application launch-pad for HTML5 apps that require authentication and enterprise-class security.
3. Azurati ASAP® HTML5 mobile enterprise application development platform for developing secure cross-platform mobile web applications.

For further information about Azurati, visit: www.azurati.com

Azurati webinar: Transforming your SharePoint Intranet to support mobile users

Register button

Vodafone recently published the results of an internal test involving 100+ staff members who were given tablets to work with.  The test showed that the following three applications were used most often by tablet users:

• Corporate email
• Intranet (SharePoint)
• Social Collaboration

The use of mobile devices in the enterprise is increasing as companies permit multiple mobile devices as part of enterprise mobile or BYOD strategies.

Mobile is key to boosting Intranet user adoption and user engagement.

Is your business ready to support mobile working?  Does your SharePoint-based Intranet address the needs of your mobile staff.

If you are responsible for your corporate Intranet or SharePoint environment, you should attend this webinar to find out how you can transform your SharePoint Intranet instantly into a secure cross-platform mobile Intranet with Azurati’s SharePoint2Go.

Register RIGHT NOW.

 

Date          Wednesday 24 October 2012
Time 14:00 London

15:00 Paris

09:00 New York

08:00 Dallas

 

 

 

 

Register button

 

COPE – Corporately owned personally enabled: the new wave in enterprise mobility

This article has been reproduced from Mobile Enterprise:

COPE – Corporately Owned, Personally Enabled

As the BYOD conversation begins to dwindle, the discussion will turn to the next wave in mobile trends: COPE (corporate owned, personally enabled). COPE gives both employers and employees the freedom of BYOD, while also offering a slew of benefits to each party.

Corporate Owned
The corporate owned (CO) portion of the COPE policy helps companies keep their networks and information secure, which has become one of the biggest backlashes of the traditional BYOD program in the workplace. CO means that the company still owns the line of service and selects its preferred device and usage cost thresholds for employees to consider.

This kind of ownership grants the company the right to wipe or disconnect devices on the corporate network, and ultimately offers pre-established security, just like the pre-BYOD days.

Personally Enabled
While 77% of BYOD employees dislike the use of MDM on their device, the personally enabled (PE) aspect of COPE allows employees to choose the company-approved device they prefer from a predetermined list, while also enabling them to use it both personally and professionally like with BYOD.

The first step in instituting COPE is for the company to select preferred devices based on what its wireless environment is suited to support. With this approach, a company can select, for example, a Blackberry 9300 at no additional cost. and

If an employee wants an iPhone, then the company only pays a predetermined amount (e.g. “cost threshold”). Employees then pay the remaining amount as outlined in the policy. This can also be implemented in a way that the company doesn’t offer any preferred device, but instead sets only a cost threshold for all users, no matter the device.

Usage costs operate similarly to cost thresholds for devices. Companies choose a predetermined amount they will pay toward usage fees, such as voice minutes, texting, data, multimedia or international plans. Whatever the company does not cover in its cost threshold for usage is the responsibility of the employee. By setting these limits, the company is able to control the outcome of each monthly bill without limiting an employee to a single device or plan.

Coping with COPE

Transitioning to this kind of program might seem like a headache, but MDM outsourcing helps IT departments seamlessly roll out COPE and maintain its features. In addition to working directly on this kind of program, MDM companies, can assist in adding more advanced features, troubleshooting, optimizing bills and handling administration.

Employee and employer benefits are plentiful. COPE doesn’t just offer the feel of a BYOD policy; it truly gives employees the opportunity to customize both their device selection and data plan with the help of their company’s IT budget.

These kinds of plans typically come with discounted offers, but it doesn’t stop there. Employees will also have the support system and help they need from their IT departments and MDM representatives, if companies choose to contract one.

Employers reap benefits all the same. Costs can be controlled and cut by pooling minutes, lowering costs per device, having manageable budgets and offering continual optimization. In some cases, giving employees the ability to customize their plans can ultimately result in productivity outside the office. With COPE, the employer also has control over things like carrier, device preference and MDM capabilities.

Azurati’s take on COPE

It does not matter what device the user is using, the key issue will be about how the user is able to connect to enterprise systems securely on mobile devices; and whether the enterprise system itself is optimized for mobile use.

If an enterprise has deployed Microsoft SharePoint, then Azurati’s SharePoint2Go® solution will provide secure access to mobile optimized SharePoint on any mobile device and without requiring MDM investments.

If employees are looking to access other core enterprise systems that are not optimized for mobile use, then Azurati ASAP® will shorten the development time to deliver secure cross-platform mobile enterprise applications.

visit www.azurati.com for more information.