Fifty Flutter Kit
17 independently versioned Flutter and Dart packages: shared visual foundations, with selectable packages for app development, game systems and receipt printing.
THE WORK
// 01 · PROBLEM · APPROACH · OUTCOME01// PROBLEM
Stop rebuilding the primitives.
i wanted the recurring pieces of an application to have a home outside the next application. colors, spacing, fields and connection handling are starting points.
putting those pieces in packages makes their boundaries inspectable. the aim is reuse without treating every application as the same problem or requiring the same dependencies.
02// APPROACH
Share values. Choose the rest.
design tokens are shared visual values. fifty_theme turns them into ThemeData, Flutter's theme configuration; fifty_ui supplies components. the foundation separates those responsibilities rather than hiding them together.
app and game packages can be selected for the work at hand. each brings its declared dependencies; selecting forms does not mean installing a dependency-free form system.
03// OUTCOME
Published separately. Inspectable together.
the checked inventory has 17 published packages: three foundation, eight app-development and six game-development packages. the repository also tracks three showcase app manifests and twelve package example manifests.
fifty_tokens 3.2.0 adds icon sizes, xxs spacing and tinted shadows. fifty_theme 3.0.1 includes a contrast-oriented color change, not a blanket accessibility certification for every palette.
STACK
// 03· WHAT IT'S MADE OFLanguageDartrequirements vary by package
FrameworkFlutterrequirements vary by package
Publisherfifty.devpublished packages
Packages17independently versioned
Foundationtokens / theme / UIthree packages
App development8 packagesrepository category
Game development6 packagesrepository category
PrintingESC/POS · Bluetooth/WiFireceipt-printer commands; hardware not exercised
Licensepackage-level MITpackage licenses, not a repository-wide audit
Packages by category.
three foundation, eight app-development and six game-development packages. categories describe the collection, not dependency wiring.
package versions are independent. these versions come from the 2026-09-07 UTC registry audit, matched to pinned source manifests; they are not a fresh latest-version check or a single kit release.
Foundation (3)
- fifty_tokens3.2.0
configurable shared visual values and JSON presets.
- fifty_theme3.0.1
design tokens converted into light/dark Material ThemeData, with brand overrides.
- fifty_ui0.7.1
reusable buttons, inputs, cards, navigation and feedback components.
App Development (8)
- fifty_forms0.2.1
field registration, validation, multi-step forms and saved drafts, with replaceable builders.
- fifty_utils0.1.2
date, duration and color extensions, responsive helpers and async state containers.
- fifty_cache0.1.1
response caching with expiry, configurable policies and memory or GetStorage backing.
- fifty_storage0.1.2
secure token storage and preferences, with initialized in-memory token reads.
- fifty_connectivity0.2.1
DNS/HTTP reachability checks, network-state monitoring and connection UI.
- fifty_socket0.1.1
Phoenix sockets with reconnect backoff, heartbeat monitoring and channel restoration.
- fifty_printing_engine1.0.3
ESC/POS receipt-printer commands over Bluetooth/WiFi, with routing and paper-size-aware tickets.
- fifty_scroll_sequence1.0.1
scroll-driven image sequences, with pinning, frame sources and image caching.
Game Development (6)
- fifty_audio_engine0.7.4
music, effects and voice channels, with crossfade, ducking hooks and saved settings.
- fifty_speech_engine0.2.1
flutter_tts and speech_to_text wrappers for speech output and recognition.
- fifty_narrative_engine0.1.2
a sequential narrative queue and state machine, with read/write/ask/wait/navigate callbacks.
- fifty_world_engine0.1.4
Flame grid worlds, JSON maps, entities, pan/zoom, pathfinding and movement ranges.
- fifty_skill_tree0.2.3
skill-tree layouts, prerequisites and progress import/export, with replaceable node builders.
- fifty_achievement_engine0.2.2
condition-based achievements, progress and prerequisite tracking, with callbacks and replaceable UI builders.
PROCESS
// 04 · SOURCE INTERFACESSource screenshots from the pinned repository, not fresh runtime captures or hardware execution. Original screenshot labels and branding are unchanged.
component gallery navigation, from buttons and inputs to feedback and layout.
UI gallery source
account-step demo UI. the email is a coded hint; the security message is static demo text, not a security guarantee.
forms screenshot source
tactical showcase source capture: turn indicator, board, units and end-turn control.
tactical screenshot source
ticket-builder text, size and alignment controls. an interface capture, not a physical printing result.
printing screenshot source
BGM player showing Void Ambient stopped, playback controls, volume, shuffle and a playlist.
fifty_audio_engine screenshot source
RPG skill tree showing 15 points and connected warrior, mage and rogue node columns.
fifty_skill_tree screenshot source
Dialogue prompt with Wisdom, Courage and Mystery choices above an empty sentence queue.
fifty_narrative_engine screenshot source
Basic Achievements showing 0 of 6 unlocked, rarity counts, click controls and achievement cards.
fifty_achievement_engine screenshot source
Pinned demo showing frame 54 of 120 on a colored panel, with Start, 50% and End controls.
fifty_scroll_sequence screenshot source
Connection Status showing WIFI, Connected: YES, an offline timer and a Check Connectivity control.
fifty_connectivity screenshot source
NUMBERS
// 05 · WHAT SHIPPEDpublished packages
17
foundation packages
3
tracked showcase app manifests
3
tracked package example app manifests
12
publication checked 2026-09-07 UTC; source counts at 9ab9a26c093b. manifests describe source inventory, not running deployments or adoption.
LESSONS
// 06 · WHAT TO TAKE FORWARD01
Separate values from presentation.
shared colors, spacing and icon sizes belong in token configuration. theme configuration and components consume those values without making every domain package part of the visual foundation.
02
Version the package, not the collection.
packages have independent versions. choose the ones an application needs and read their dependency constraints; fifty_forms also brings foundation and storage dependencies, not isolation from the rest.
03
Leave the UI replaceable.
forms, skill trees and achievements expose builder hooks. their default presentation is a starting point; application-specific views need not become a fork of the underlying package.
04
Make the examples inspectable.
three showcase app manifests and twelve package example manifests expose how pieces are assembled. inspectable source is useful evidence of structure, not evidence that a build or integration passed.
Need a kit like this?
building a Flutter application with shared UI, game systems or receipt printing? let's discuss which pieces belong in your project.
FIFTY FLUTTER KIT●DART●FLUTTER●17 PACKAGES●FIFTY FLUTTER KIT●DART●FLUTTER●17 PACKAGES●