Mobiconf 2018: Jan Hudzik, Miquido
summary
Most mobile projects use permissive licenses — about 75% of GitHub projects and roughly 95% of mobile cases — which allow commercial use but require attribution (an in‑app libraries/licenses screen with license text). Copyleft licenses like GPL copyleft forces publish source can obligate releasing app source, so avoid them for commercial apps or consult a lawyer. Check the artifact page or LICENSE file before adding a dependency, use tooling (Gradle plugin, aboutlibraries and attribution-presenter, CocoaPods plist) and block no‑license code; automate checks in CI.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 1:38Why legal side matters in software
- 7:27Types of software licenses overview
- 9:54Public domain and permissive licenses
- 16:29Copyleft licenses explained
- 19:22Proprietary and trade secret licenses
- 21:31Handling unlicensed software
- 23:40Practical license checks in mobile dev
- 33:40Documenting and maintaining licenses
- 35:05Key takeaways and Q&A
related talks
14mOpen Source Licensing in a Business World
49mLicense to Kill One's Code
29mHey Kid! Don't Copy That Floppy!
57mWhat You Need to Know About Open Source—Trust Me, I'm a Lawyer
42mOpen Source Licenses: Between Parish Wars and Radicalism
13mBuild license management into your pipelines
01h 38mOpen Source Licensing: Types, Strategies and Compliance
16mDeploying LLM on prem: let's review licenses and highlight open source technologies