# Blueprint: the Android dashboard template icon pack authors actually ship with

> Blueprint is a Kotlin Android dashboard for icon packs, published as a library over Maven so an app can adopt the home, icons, apply, requests, help, credits and settings screens. The trade-off is that the custom licence in LICENSE.md has to be read before you fork it, and the project leans on a companion icon request service.

**jahirfiquitiva/Blueprint** — Free, feature-rich, easily customizable Android dashboard for icon packs

- Repository: https://github.com/jahirfiquitiva/Blueprint
- Website: https://dashbud.dev
- Stars: 942 · Forks: 174
- Language: Kotlin
- License: NOASSERTION
- Published: 2026-10-20 · Updated: 2026-10-20 · Language: en
- Canonical page: https://hysenlabs.com/projects/jahirfiquitiva-blueprint

## A dashboard, not an icon pack

The one-line description on the repository is a free, feature-rich, easily customizable Android dashboard for icon packs, and that framing sets the scope precisely. Blueprint is the shell around an icon pack: the home screen, the icons listing, the apply section where users push a pack to their launcher, the request tool, the help section, the credits and the settings. The project topics list klck, kustom, kwgt, kwlp, muzei and zooper alongside widgets and wallpaper tooling, which is a hint about the design language and the wallpaper ecosystem it plugs into. The primary language is Kotlin, the API badge reads 21 and up, and the README states that the app works with Android 5.0 and newer. If you are an icon pack designer with no interest in writing a settings screen, a licence checker and a launcher integration from scratch, this is the part someone else already wrote.

## The apply section is where the real work sits

The feature list calls out an apply section with 20 supported launchers, and immediately adds the caveat that other launchers might not support direct apply. That single line tells you most of what you need to know about the difficulty of this project. Direct apply means the dashboard sends the icon pack to a specific launcher over an intent, and each launcher exposes a slightly different contract, so the supported set is a maintained list of one-off integrations rather than a single generic mechanism. A dashboard that claims 20 launchers has to keep 20 code paths in step with launcher updates, and the README notes that support for adaptive icon packs is present with additional improvements coming soon. The related work in the same ecosystem is delegated rather than reinvented: wallpapers support is based on Frames, and templates support is based on Kuper, both by the same author. Blueprint is therefore a composition of focused libraries plus the glue an icon pack app needs.

## Icon requests run through a companion service

The in-app icon request tool is listed among the features, and the README spends a section on Pacific Manager, a separate service that takes over handling those requests. The pitch is stated plainly: it handles icon requests so you can quit the traditional method of receiving emails from users and sorting through potentially duplicate requests a day. The README also notes a checkout code blueprint that gives 2 weeks of Pacific Manager for free. Two consequences for an adopter. First, the request workflow has a service dependency, so the dashboard is not a self-contained piece of software. Second, the walls feature is described as cloud based only, which is a separate constraint from the request service and applies to wallpapers rather than to icons. The app can work offline, which covers the browsing and settings parts, but any feature that reaches the network needs connectivity, and the documentation does not describe a local fallback for requests.

## Adding Blueprint to a project over Maven and Jitpack

The library is published through Maven Central and Jitpack, and the documentation gives two Gradle steps. First, both repositories must be present in the root build.gradle file.

```gradle
allprojects {
    repositories {
        mavenCentral()
        maven { url 'https://jitpack.io' }
    }
}
```

Second, the AAR is added as an implementation dependency with transitive resolution enabled.

```gradle
dependencies {
    implementation('dev.jahir:Blueprint:{latest version}@aar') {
        transitive = true
    }
}
```

The placeholder {latest version} corresponds to the published version on the GitHub Releases page. The repository root holds a build.gradle, a settings.gradle.kts, a buildSrc directory and a gradle directory with the gradlew wrapper, so the project is a standard Gradle build. One detail worth noting: the default branch is sample, not master or main, which is unusual and worth checking before you file a pull request.

## Localisation, theming and tablet layouts are the customization surface

The settings section lists an option to change the app theme with Light, Dark, System and AMOLED choices, an option to colour the navigation bar on Lollipop and newer, and an option to clear the app cache. Tablet layouts are called out as supported. The theme options matter for an icon pack, because the dashboard is the one screen where the user sees your brand next to their icons, and AMOLED mode is the option that usually decides whether a dark dashboard looks deliberate. Crowdin handles translations, and the README invites contributors to the translation site, so the localisation pipeline is already wired up rather than something a fork would have to invent. The wallpaper side adds a full-screen viewer with zooming and a detailed info viewer, and wallpapers can be applied and downloaded. Credits, help and a request tool round out the screens, which is the concrete sense in which this is feature-rich rather than a single-purpose template.

## A custom licence, MIT-style libraries elsewhere, and a paid service in the loop

The licence field on the repository says Other, a custom licence GitHub cannot classify, and the LICENSE file is LICENSE.md at the root rather than a standard text file. That is the single most important item to check before you ship anything, and it is different from the permissive licences most Android libraries carry. Read LICENSE.md and compare it with your distribution model rather than assuming it is Apache or MIT. The README also links to a donation page, a GitHub Sponsors profile and a Discord server for support, so the project is maintained by one developer, Jahir Fiquitiva, with community help offered through chat. The README points to a wiki for implementation details and shows a list of other apps built with the dashboard, which tells you the pattern is real and repeated. Recent releases show v2.5.0 on 2025-08-17, v2.5.1 on 2025-12-29 and v2.6.0 on 2026-10-11, with the last push on 2026-10-11, so the project is being shipped rather than abandoned.

## Where this is the wrong choice

There are cases where Blueprint is a mismatch. If your app is not an icon pack, a dashboard built around pack applying, a licence checker and icon requests is the wrong shape of dependency. If you need the request system to run entirely on your own infrastructure, the Pacific Manager dependency is a problem, and the documentation describes no self-hosted option for it. If your users are on launchers outside the supported 20, the central promise of the apply flow weakens, and the README is honest that other launchers might not support direct apply. Finally, if your organisation requires a recognised OSI licence or a security review of an external AAR, the custom licence in LICENSE.md and the fact that the dependency pulls transitive artifacts both need checking by whoever handles that. A dashboard is presentation, but this one carries a launcher-integration surface and two networked features, so it deserves the same scrutiny as any other third-party dependency you ship inside your app.

## Conclusion

Blueprint fits an author of an icon pack who needs a presentable dashboard without designing seven screens, and it does not fit a team that needs an Apache or MIT licensed base or a fully self-hosted icon request workflow, because requests lean on Pacific Manager and the licence is a custom one in LICENSE.md. Before you add the dependency, read LICENSE.md against your distribution model, confirm your icon pack targets API 21 and up as the badge states, and check the apply section against the exact launchers your users run, since the documentation claims 20 supported launchers and says other launchers might not support direct apply.

## FAQ

### How do I add the Blueprint library to an Android project?

Add MavenCentral and Jitpack to the repositories block of your root build.gradle file, then add the AAR as an implementation dependency with transitive = true, using the published version in place of {latest version}.

### What does the Blueprint dashboard include for icon pack authors?

It includes home, icons, apply, requests, help, credits and settings screens, an apply section supporting 20 launchers, a licence checker, donations and OneSignal notifications ready, plus support for adaptive icon packs, Zooper templates, Kustom wallpapers, widgets, lockscreens and Komponents.

### How are icon requests handled in Blueprint?

The in-app icon request tool is supported, and the README points to Pacific Manager, a separate service that takes care of icon requests so you do not have to sort through email requests. Wallpapers are described as cloud based only, although the app itself can work offline.

### Which Android versions does Blueprint support?

The API badge states 21 and up, and the feature list says the app works with Android 5.0 and newer. The project is written in Kotlin.

## Sources

- [Issues](https://github.com/jahirfiquitiva/Blueprint/issues)
- [jahirfiquitiva/Blueprint on GitHub](https://github.com/jahirfiquitiva/Blueprint)
- [Project website](https://dashbud.dev)
- [README](https://github.com/jahirfiquitiva/Blueprint/blob/sample/README.md)
- [Releases](https://github.com/jahirfiquitiva/Blueprint/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/jahirfiquitiva-blueprint