Companies are now warming up to the idea of bring your own device (BYOD) to work. After all, can you blame a CEO or small business owner for salivating over the opportunity to cut capital costs on computer hardware and connectivity, when an employee willingly wants to use their own stuff?
How does BYOD fit into your mobile development plans? Tell me by posting a comment below.
As expected, IT departments far and wide are pretty skittish about the prospect of supporting numerous devices, operating systems and one-off applications. Mobile development, at all levels, will have to be very smart about application effectiveness, deployment, support, connectivity issues, security, regulations, compliance and convenience.
Indeed, in “BYOD Failure – Five Big Reasons Why Employees Don’t Want To Use Their iPhones, iPads At Work” Ryan Faas of Cult of Mac raises questions of restricted feature access, the possibility of remote wipes, snooping and other issues. This is nothing new in the PC desktop and laptop world. But is there any difference between with smartphones and tablets?
Mobile developers will have to face tough decisions balancing the needs of the users against the policies and desires of employers.
Let’s not forget that mobile developers, including many in their 20s and 30s, have grown up with ubiquitous connectivity and “root” access to their devices, including desktops, laptops, smart phones and tablets. How will being “inherently mobile” affect their view of mobile development when it comes to their own company’s policies and the social media aspects of devices?