There has been a lot written about the benefits of native vs. web (HTML) applications for the mobile enterprise. This article is not aimed at pushing the pros or cons of each model, but rather exploring what may be the hidden costs of developing mobile applications natively. 

HTML has been around as long as the web. So what's all the fuss about? HTML5 is yet another standard for web content that is aimed at delivering a common user experience regardless of browser. By doing so, the web community is aiming to enable application/web developers to produce an experience that is acceptable to browsers on Smartphones and tablets. While this in itself may not sound like much….it is. 

Bring Your Own Device (BYOD) has become a common catchphrase that many CIOs are hearing, and fearing. How on earth can Smartphones or tablets, which are fast becoming cut-down personal computers, be allowed onto a corporate network? What about security…SOE…support? This shift in thinking is part of what many are calling the consumerization of IT. Corporate employees want a "consumer experience" at work…and using their own phone to access corporate data is part of that.

The Cloud. It seems that in today's ever-changing IT world, everything can now be cloud-based. We have all varieties of IT services now available "on demand." So, what about enterprise mobility? Can mobile enterprise applications be made available as a service and, if so, what needs to be taken into consideration when deciding between on-premise and cloud-based solutions? Here are a few suggestions for you to consider.

Has your organization mobilized SAP? Share your insights and click here to take the Mobile Outlook 2012 survey today.

SAPinsider and insiderRESEARCH have partnered with top mobility analyst Kevin Benedict to survey SAP customers regarding enterprise mobility and explore the findings in the Mobile Outlook 2012 report. Sky Technologies is excited to announce that we’ve signed on as a sponsor of this comprehensive study.

Enterprise mobility projects come in a variety of sizes using many different methodologies. An agreement should have been reached in the earlier phases of the project on strategically how the blueprint and design phase is to be undertaken. Now is the opportunity to move past the strategy and into the reality, at least for the process and application design. 

You may have already heard that Sky Technologies has announced some exciting new developments recently. For those of you that haven’t, here’s a quick summary

In your enterprise mobility project, one of your goals is most likely to get the most out of your business process as possible. However, before you start mobilizing, it may be a good idea to first step back and assess your current process as it stands. After all, how much you benefit from mobilizing a process goes back to the quality of the process itself. While mobilizing an existing process is undoubtedly less expensive and risky, you may want to consider re-engineering the process if it’s lacking or could use some updating or cleaning up.

Mobility introduces a host of new concepts when it comes to data and considering where and when it should be available.  Many of us have spent years convincing businesses to rationalize and centralize into single, central global data centers. All the big back-end systems vendors, SAP included, sell themselves on getting data off personal PCs and centralizing it. Organizations have laid ground rules and procedures to support this cause, and for a good reason.

UW5JNF9WB63R

Once you’ve gone through the RFP process, secured funding, and selected a solution for the mobile enterprise project, you’re ready to get started right? Not quite, there’s still one more step, and that’s to get everyone on the same page.