A modern programming language that makes developers happier.

kotlinlang

any suggestion/references to create an android documentation with backend APIs is called in a particular Activity

context: this documentation will be consumed by the Product, Design or even a different team (or for our future self/onboarding process)

e.g:
1. Backend Devs, Web Devs to know which API is used in this Android screen
2. Product/Design/QA: to understand which endpoint path is called in the particular android screen, request/response payload is used (required/optional for QA to check it’s returned from Backend or not)
please refer me to the right channel if this is not the right one :pray: