'JetPack Compose for library development
We are about to start greenfield development of an Android library and considering using JetPack Compose for UI elements used there. I know that one restriction to consider is API 21+ (not really a problem). Are there any other reasons to use or not use Jetpack Compose for library development?
Solution 1:[1]
Well I'm not sure if that's a definite "no" for usage (that's rather subjective), but you have to bring the dependency on the compose along with the library. This will affect the library and app size
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Jakoss |