AnyPass (Work In Progress ⛏)
AnyPass is your one-stop solution for password management, password generation, and password health analysis.
The app architecture has three layers: a data layer, a domain layer and a UI layer. Cosmo uses Meteor KMP to create application using MVI architecture. It provides a unidirectional data flow (UDF), allowing you to handle state changes and propagate them to the UI efficiently.
Single source of truth
When a new data type is defined in your app, you should assign a Single Source of Truth (SSOT) to it. The SSOT is the owner of that data, and only the SSOT can modify or mutate it. To achieve this, the SSOT exposes the data using an immutable type, and to modify the data, the SSOT exposes functions or receive events that other types can call.
This pattern brings multiple benefits:
- It centralizes all the changes to a particular type of data in one place.
- It protects the data so that other types cannot tamper with it.
- It makes changes to the data more traceable. Thus, bugs are easier to spot.
In an offline-first application, the source of truth for application data is typically a database. In some other cases, the source of truth can be a ViewModel or even the UI.
Modularization is the practice of breaking the concept of a monolithic, one-module codebase into loosely coupled, self contained modules.
A barebone module is simply a directory with a Gradle build script inside. Usually though, a module will consist of one or more source sets and possibly a collection of resources or assets. Modules can be built and tested independently. Due to Gradle’s flexibility there are few constraints as to how you can organize your project. In general, you should strive for low coupling and high cohesion.
- Low coupling – Modules should be as independent as possible from one another, so that changes to one module have zero or minimal impact on other modules. They should not possess knowledge of the inner workings of other modules.
- High cohesion – A module should comprise a collection of code that acts as a system. It should have clearly defined responsibilities and stay within boundaries of certain domain knowledge.
graph TD; core-->common; core-->designsystem; core-->analytics; designsystem-->shared; common-->shared; analytics-->shared;
graph TD; manager-->password; manager-->biometry; features-->generatepassword; password-->generatepassword; biometry-->shared;
graph TD; data-->local; data-->authManager; data-->settings; features-->onboarding; features-->auth; features-->addnewpassword; features-->home; features-->auth; settings--> features; local-->features; authManager-->features; onboarding-->shared; auth-->shared; home-->shared; addnewpassword-->shared;
graph TD; features-->onboarding; features-->auth; features-->addnewpassword; features-->home; features-->auth; features-->space; features-->generatepassword; onboarding-->shared; auth-->shared; home-->shared; addnewpassword-->shared; space-->shared; generatepassword-->shared;
- Java 17+
- iOS: 14.0+