![]() ![]() Release app as another Apache 2.0? project (My guts say no).Release device and domain as a Apache 2.0? project (My guts say yes). ![]() Given only data uses a AGPLv3.0 library, could we: "thou shalt not use AGPL, GPL or LGPL dependencies." Unless you are using a permissive dependency, the viral nature of (L)GPL forces the developer publish the whole app content, i.e. Unlike *.deb or *.rpm packages in a common Linux distribution, Android apps required static linking to its dependencies. Permissive vs Strongly Protected Licenses device depends on domain interfaces only.All modules depended on domain because app, data and device implement interfaces defined by domain.With no Android framework dependencies at the domain module, the network/cache and sensors boilerplate moved into data and device modules respectively. One of the many reasons for adopting architecture on Android apps is simplify testability isolating the business cases code from modules that require Android dependencies.īusiness cases (or interactors) are implemented like command pattern instances. We are considering creating a series of dependency modules (UI, repository patterns, etc) as separated Android libraries.Ĭould we use a permissive license (Apache 2.0, BSD-2 or MIT) despite statically linking them into another AGPL v3.0 app project? Details Android Clean Architecture
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |