Package selection guidance compiled from public package information, community data, and project usage.
Neat Cache is a clean, abstraction layer for managing in-memory and Redis-based caching in Dart applications. It provides a consistent interface to interact with different cache backends, simplifying the implementation of efficient data storage and retrieval. Designed for simplicity and performance, it supports common operations like get, put, and remove, while abstracting underlying complexities. Ideal for apps needing fast access to frequently used data across multiple platforms.
Use cases
Caching API responses
Storing user session data
Reducing redundant database queries
Improving app startup speed
Managing temporary application state
Key features
Unified interface for in-memory and Redis caches
Simple get/put/remove operations
Cross-platform compatibility
Lightweight and easy to integrate
Supports expiration and eviction policies
Suitable for
Developers building scalable Flutter apps
Teams using Redis in backend services
Applications requiring fast local data access
Projects prioritizing clean code architecture
Backend-integrated mobile or desktop apps
Considerations
Requires setup of Redis if using remote caching
Limited to supported platforms (Android, iOS, macOS, Windows, Linux)
Not suitable for large-scale persistent storage
Depends on external Redis server for distributed use
May need additional configuration for advanced cache strategies
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
Dart Neats
A collection of a small neat packages for dart.
Disclaimer: This is not an officially supported Google product.
This repository is meant as a playground where small neat packages are
cultivated. If package grows too large and complex and needs a dedicated issue
tracker it should be moved to a dedicated repository.
Each folder in this repository contains a neatpub package. This project
aims to use a separate package whenever it makes sense to have an independent
major version. This often means splitting functionality into separate packages,
which can be reused independently.
Utility for vendoring packages into a project and rewriting import/export statements.
Repository Management
Packages in this repository uses pub workspaces
a single dart pub get will resolve dependencies for all of them.
Configuration of Github Actions, issue templates, issue labels, etc is automated
with scripts in tool/.
Contributing
We love patches and contributions, please refer to CONTRIBUTING.md for
technicalities on CLA and community guidelines. As this project aims to
build neat packages using other neat packages we might also accept proposals
for new neat packages, though it's often easier to publish independently.
License
Unless stated otherwise contents in this repository is licensed under
Apache License 2.0, see LICENSE.