Open source in mobile apps: A best practices guide

By Suzanne Kattau

May 30, 2012 — (Page 1 of 3)
The use of open-source code in mobile app development is exploding. Flexibility, increased innovation and shorter development times are just three reasons developers are turning more frequently to open source.

According to the sixth annual Future of Open Source Survey, recently conducted by North Bridge Venture Partners and Black Duck Software in conjunction with The 451 Group, open-source software (OSS) investment increased by 49% to US$675 million in 2011. The quality of open source—and the ability to continuously improve it—are two of the top reasons for its adoption, the survey said.

With more than 10,000 new mobile open-source projects launched in 2011 (bringing the cumulative total to over 18,000, according to Black Duck’s KnowledgeBase), the use of open-source software in mobile app development shows no signs of slowing down.

“Open source is the foundation for mission-critical apps in the enterprise,” said Rod Cope, founder and CTO of OpenLogic, a provider of enterprise open-source software scanning and governance solutions. “Nearly all mobile developers are now using open source.”

“There’s so much good code available in the public domain,” added Mahshad Koohgoli, CEO of Protecode, a provider of open-source license-management solutions. “Good developers don’t write code from scratch anymore; they know how to find that code.”

This trend of using open-source code in mobile app development is bringing to light new legal responsibilities and design considerations for app developers. As a developer, you should know the following best practices for successfully using open-source code in mobile apps.

One best practice is to choose a basic development approach at design time. “The first step is to evaluate the size and depth of your project,” said Dave Gruber, director of developer relations at Black Duck, a provider of solutions for automating the management, governance and secure use of open-source software. “Decide early on just how much code you will do natively and how many open-source components you plan to use in your mobile app.”

Another best practice is to learn your company’s open-source license policy before you begin development. “Your company should have an open-source license policy set in place,” said Gruber. “Make sure you understand the policy so as to avoid a negative code audit at build time. Know if you will be using the Apache license, the Mozilla license or other licenses.”

Do you know which open-source licenses your company wants you to comply with? There are thousands of licenses in existence, so it’s important to find out. Among the most popular open-source licenses are the Apache License, the Mozilla Public License, the GNU General Public License (GPL), and the GNU Lesser General Public License (LGPL). The GNU Project (a free-software, mass-collaboration project) offers a list of GPL-compatible free software licenses on its website.

Related Search Term(s): app stores, open source

Pages 1 2 3

Share this link: http://sdt.bz/36660

Technorati

Digg

Slashdot

Facebook

Friendfeed

Twitter

del.icio.us

SD Times Blog: Microsoft Open Tech turns one Subsidiary advances Microsoft's cooperative stance toward open source

Git changes how developers manage source code versions At this year's Git Together, developers praise the platform's convenience and its ability to make source control easier. Changes for the future will focus on making it more Web 2.0-compatible by offering more on-demand repositories on GitHub.

Open source is done. Welcome to open development Without bosses or overly centralized structures, developers can be more productive