russhwolf
commented
2 years ago Notes/TODOs from my docs audit:
overall
- unify usages of “KaMPKit” vs “KaMP Kit” vs “The KaMP Kit”
other stuff to add
- notes on binary size concerns?
readme
- update goal
- our arch recommendations
- our forward-looking expectation of what prod needs will look like
- update dev env
- IDE versions etc
- update background education section
- strip concurrency stuff
- other intro resources?
- more integration notes?
contact us
- maybe add notes about github issues and what does and doesn’t belong
- redirect to slack/SO for general KMP help that's not KaMPKit-specific
app_build
- looks mostly accurate
- add notes on ci hosts?
debugging_kotlin_in_xcode
- add notes about CLI and other recent updates
detailed_dev_setup
- talk about android studio vs intellij tradeoffs
- add notes on kdoctor
- link to infoq article is probably out-of-date
general_architecture
- add more details on theory behind viewmodel sharing
- add more details on coroutine interop
- update coroutines notes to take new mm into account
- update dependencies
- mention turbine
- de-emphasize stately
- update testing to take into account coroutines advances
ios_proj_integration
- drop mentions of old cocoapods fork
- update config sample to match recent plugin version
- talk about static vs dynamic tradeoffs
troubleshooting
- scan recent issues and slack convos for other tips
what_and_why
- probably mostly good but it’s still a 2019 perspective
- maybe keep existing doc for historical purposes and add a new intro with current context/thinking
samhill303
KatieGalvin
Review and define what we want to do with the KaMP Kit docs. The repo is moving from an un-opinionated KMP implementation into something closer to what we'd do for KMM. Should still be a good first stop for KMM, however.