All tests run on an 8-year-old MacBook Air (Intel). The apps are lightweight and fast, but they're also designed to make you smile while debugging at 2 AM.
Developer tools have an aesthetic problem. They're either sterile gray panels or overwhelming dashboards crammed with every possible option. When I started building macOS utilities for Android development, I made a deliberate choice: these tools would be technically superior and visually friendly. "Hiyoko" (ひよこ) means "chick" in Japanese—small, agile, and approachable. That name became a design philosophy.
TL;DR
- "Cute" branding reduces cognitive fatigue during long debugging sessions—it's a UX decision, not just decoration.
- Consistent design tokens (colors, spacing, typography) across 10 apps create a recognizable ecosystem.
- Custom audio feedback ("Piyo!" chirp) turns mundane notifications into moments of delight.
- Glassmorphism and translucent popovers make tools feel native to modern macOS.
Why Developer Tools Don't Have to Be Ugly
Most developer tools default to one of two extremes: enterprise gray (think Jenkins) or terminal minimalism (plain CLI output). Both are functional, but neither respects the fact that developers spend 8+ hours a day staring at these interfaces.
Research on developer experience shows that visual comfort directly impacts sustained focus. A tool that feels pleasant to use gets used more consistently. A tool that feels like a chore gets replaced by a terminal alias.
I chose a third path: tools that look approachable but don't compromise on technical depth.
The Design Token System
Every Hiyoko app shares a core set of CSS custom properties. This isn't just for visual consistency—it cuts development time when building new apps.
/* hiyoko-design-tokens.css — shared across all 10 apps */
:root {
/* Suite-wide base palette */
--hiyoko-bg-primary: rgba(30, 30, 30, 0.92);
--hiyoko-bg-glass: rgba(255, 255, 255, 0.06);
--hiyoko-border-subtle: rgba(255, 255, 255, 0.08);
--hiyoko-text-primary: #e8e8e8;
--hiyoko-text-secondary: #8b8b8b;
--hiyoko-radius-md: 10px;
--hiyoko-shadow-popover: 0 8px 32px rgba(0, 0, 0, 0.4);
/* Per-app accent colors */
--accent-mtp: #4a9eff; /* HiyokoMTP — blue */
--accent-logcat: #ffd44a; /* HiyokoLogcat — yellow */
--accent-shot: #ff6b8a; /* HiyokoShot — pink */
--accent-pdf: #7c5cfc; /* HiyokoPDFVault — purple */
--accent-sync: #4adb8b; /* HiyokoAutoSync — green */
}
/* Glassmorphism popover — reused in HiyokoShot, HiyokoBar, HiyokoClip */
.hiyoko-popover {
background: var(--hiyoko-bg-glass);
backdrop-filter: blur(24px) saturate(180%);
-webkit-backdrop-filter: blur(24px) saturate(180%);
border: 1px solid var(--hiyoko-border-subtle);
border-radius: var(--hiyoko-radius-md);
box-shadow: var(--hiyoko-shadow-popover);
}
When I build a new app, I import this token file and the base layout is already 80% done. Each app gets its own accent color, but the typography, spacing, and glass effects are identical.
The "Piyo" Notification
Here's a small detail that gets more positive feedback than almost any feature: custom notification sounds.
When HiyokoShot finishes capturing a screenshot, instead of the default macOS "ding," users hear a soft "Piyo!" chirp. It's a tiny MP3, but the effect is outsized.
// Playing the "Piyo" chirp on task completion
use tauri::Manager;
#[tauri::command]
async fn play_notification_sound(app: tauri::AppHandle) -> Result<(), String> {
let resource_path = app
.path()
.resource_dir()
.map_err(|e| e.to_string())?
.join("sounds/piyo.mp3");
// Use macOS native audio playback via NSSound
std::process::Command::new("afplay")
.arg(&resource_path)
.arg("-v")
.arg("0.5") // half volume — subtle, not jarring
.spawn()
.map_err(|e| e.to_string())?;
Ok(())
}
The key design decision: the sound is subtle. Half volume, short duration. It signals "done" without demanding attention. Users can disable it in settings, but almost nobody does.
UX over Feature Count
"Serious" tools often compete on feature count. Hiyoko tools take the opposite approach: prioritize the 3-5 actions developers do most, and make those actions frictionless.
For HiyokoShot, that means:
- Click the menu bar icon → screenshot captured and transferred → "Piyo!" → done.
- No configuration wizard. No "choose your output format" dialog on first launch.
- Advanced options exist, but they're one level deep in a settings panel.
This philosophy comes from a practical place: on my 8-year-old MacBook Air, every unnecessary UI element is wasted RAM and CPU. Minimal UI isn't just aesthetic—it's a performance requirement.
You don't need a cold, gray interface to build "real" tools. Developers are humans who respond to thoughtful design. The Hiyoko Suite proves that approachability and technical depth aren't mutually exclusive—they reinforce each other.
Do your favorite developer tools have any personality, or are they all function-over-form? I'd love to hear what makes a tool "feel right" to you.
If this was helpful, check out HiyokoShot — Android screenshot transfer via USB or Wi-Fi.
Built with Rust + Tauri v2. Tested on an 8-year-old MacBook Air.
