back to home

nickbutcher / plaid

An Android app which provides design news & inspiration as well as being an example of implementing material design.

16,216 stars
3,105 forks
102 issues
KotlinJavaHTML

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing nickbutcher/plaid in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/nickbutcher/plaid)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

\[ 🚧 Work in progress šŸ‘·ā€ā™€ļøā›šŸ‘·šŸ”§ļøšŸ‘·šŸ”§ 🚧 \] Plaid 2.0 Rewriting Plaid using Android Architecture Components, in Kotlin. šŸ‘€ "Up for grabs" issues – We're happy to get your contributions on those! šŸ‘ Comments and new issues created are welcomed. šŸ›‘ We're currently not accepting external PRs that touch on the app's architecture. Background Plaid was written with one big goal: showcase material design in Android in a real application. While Plaid successfully achieved its goal, from an architecture point of view, it lacks all features that would make it a modular, scalable, testable and maintainable app: with UI logic in Android classes, no tests and only one module. Plaid represents a great real world app example: it provides a fairly complex set of functionalities, it has technical debt, it has features that have to be dealt with as APIs are being removed. All of these problems are encountered by many projects in the Android community and therefore, make Plaid a suitable showcase for all the advantages that architecture components bring. More information • Read more: • Restitching Plaid - Updating Plaid to modern app standards • A patchwork Plaid - Monolith to modularized app • Cross-stitching Plaid and AndroidX • Dependency injection in a multi module project • Video Presentations: • Shaping Your App's Architecture with Kotlin and Architecture Components by Florina (Florina Muntenescu at KotlinConf 2018) • Re-stitching Plaid with Kotlin (Florina Muntenescu at Android Dev Summit '18) Goals • Migrate Plaid to Architecture Components. The refactoring will follow the architecture described in Guide to App Architecture. • Convert to Kotlin, while migrating to Architecture Components. • Modularize the app using dynamic feature modules. • Showcase the extensibility of the architecture by adding an extra data source, once the migration is finished. Non-Goals Changes to the styles, themes, icons, animations, transitions or any other UI elements that were the initial focus of Plaid, are outside the scope of this refactoring. Android Studio IDE setup Plaid requires Android Studio version 3.6 or higher. Plaid uses ktlint to enforce Kotlin coding styles. Here's how to configure it for use with Android Studio (instructions adapted from the ktlint README): • Close Android Studio if it's open • Download ktlint using these installation instructions • Inside the project root directory run: • Remove ktlint if desired: • Start Android Studio --- Plaid 1.0 *Design news and inspiration.* Plaid is a showcase of material design that we hope you will keep installed. It pulls in news & inspiration from Designer News, Dribbble & Product Hunt. It demonstrates the use of material principles to create tactile, bold, understandable UIs. **Install on Google Play (Beta Testing)** Screenshots Non-Goals Plaid is a UI sample and seeks to demonstrate how to implement material design. To make this as clear as possible it explicitly does not attempt to: • Provide opinionated **architecture/testing** advice; it utilizes vanilla Android components. For advice on this, I'd recommend Blueprints. • Support **pre-Lollipop** devices. Doing so is entirely possible, but complicates things. For advice on doing this, see this fork. License