Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Contribute to OpenSource writing (Kotlin friend...
Search
Paolo Rotolo
July 20, 2018
0
100
Contribute to OpenSource writing (Kotlin friendly) libraries for Android
Presented at Campus Party Italy 2018.
Paolo Rotolo
July 20, 2018
Tweet
Share
More Decks by Paolo Rotolo
See All by Paolo Rotolo
A guide to Android Background Work
paolorotolo
0
150
Kotlin Multiplatform for Android/iOS devs v2
paolorotolo
1
72
Kotlin Multiplatform for Android/iOS devs
paolorotolo
1
240
State Management in Flutter (Flutter Festival Bari)
paolorotolo
0
340
Coroutines and Flow integration with Android Architecture Components
paolorotolo
1
550
Survive the Android Memory Killer
paolorotolo
0
49
Test and automate Android Development with CI magic
paolorotolo
0
120
Featured
See All Featured
How to Think Like a Performance Engineer
csswizardry
22
1.2k
Art, The Web, and Tiny UX
lynnandtonic
298
20k
Adopting Sorbet at Scale
ufuk
73
9.1k
Raft: Consensus for Rubyists
vanstee
137
6.7k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
47
5.1k
What’s in a name? Adding method to the madness
productmarketing
PRO
22
3.2k
Stop Working from a Prison Cell
hatefulcrawdad
267
20k
Gamification - CAS2011
davidbonilla
80
5.1k
Docker and Python
trallard
42
3.1k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
229
52k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
5
450
XXLCSS - How to scale CSS and keep your sanity
sugarenia
247
1.3M
Transcript
Contribute to open source writing (Kotlin-friendly) libraries for Android @PaoloRotolo
Paolo Rotolo #CPIT2
About me
None
None
Make an Android Library
// build.gradle // day 1
// build.gradle // day 10
None
None
Build an Android Library
Why I have to develop a library?
Why I have to develop a library for free?
Writing a modular project - Faster gradle builds - Easily
pluggable into Instant apps - Better team work, as one person can have the sole responsibility of a module - Smoother git flows - Easy to create libraries from code :D
Each module (library) should solve a single specific issue
None
None
None
// build.gradle // BEFORE
// build.gradle // AFTER
Choose resources to make public
All resources in a library default to public
None
None
Publish your library
Name your library
Name your library ;)
None
ShapeOfView
GlideToVectorYou
Publish your artifact
None
None
None
Test your library
Test your library BONUS: it’s easy if OpenSource ;)
Document your library
Write a good README
Write a good README
Maintain your library
- Close issues on GitHub; Maintain your library
Maintain your library
- Close issues on GitHub; - Accept/reject pull requests; Maintain
your library
- Close issues on GitHub; - Accept/reject pull requests; -
Release new versions Maintain your library
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
Android KTX
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
Questions?
[email protected]
@paolorotolo