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
110
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
74
Kotlin Multiplatform for Android/iOS devs
paolorotolo
1
270
State Management in Flutter (Flutter Festival Bari)
paolorotolo
0
350
Coroutines and Flow integration with Android Architecture Components
paolorotolo
1
560
Survive the Android Memory Killer
paolorotolo
0
50
Test and automate Android Development with CI magic
paolorotolo
0
130
Featured
See All Featured
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
175
51k
Intergalactic Javascript Robots from Outer Space
tanoku
270
27k
What's in a price? How to price your products and services
michaelherold
244
12k
Code Review Best Practice
trishagee
67
18k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
226
22k
Building Your Own Lightsaber
phodgson
104
6.2k
Unsuck your backbone
ammeep
669
57k
Practical Orchestrator
shlominoach
186
10k
StorybookのUI Testing Handbookを読んだ
zakiyama
28
5.5k
Fantastic passwords and where to find them - at NoRuKo
philnash
51
3k
The Invisible Side of Design
smashingmag
299
50k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
59k
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