Blog archive, page 5

A close view of a smartphone home screen filled with app icons on a pale table. The phone is where a short business bot has to earn a place among tools people already open.

September 26, 2026Automation

What a Telegram bot is good for

A Telegram bot fits a known group and a short command list: status, intake, and alerts. It is a poor substitute for a product that should be a screen.

By Hanabi

Two people pointing at a laptop screen, one wearing a fitness band. They are looking at one screen together, the scale of a first automation.

September 26, 2026Automation

Start AI automation with one boring workflow

Start AI automation with one repeated chore that has a clear input and a clear output. Skip the platform that promises to automate the whole company.

By Hanabi

A person gesturing in a meeting, with a laptop showing a colorful layout, a notebook, and a phone on the table. The meeting ends, and someone still has to keep the system current.

September 26, 2026Design systems

How a brand kit stays alive after launch

A brand kit stays alive when one person owns changes and the files live where the team already works. A zip file in a chat thread will fork.

By Hanabi

Hands sketching a user-flow diagram labeled user goals on a sheet of paper. The drawing follows one set of marks, which is the same discipline an icon set needs.

September 26, 2026Design systems

Icons and illustration as part of the system

Pick one stroke, one grid, and a limit on what icons may depict. Mixing three downloaded styles makes a product look assembled rather than designed.

By Hanabi

A long, quiet office corridor with glass rooms, a teal sofa, and a dark kitchen. Light rooms and a dark kitchen share one building, the way two themes should share one system.

September 26, 2026Design systems

Dark mode as a system decision

Dark mode is a second set of color decisions, planned with the light palette. A filter at the end inverts the product instead of designing the pairs.

By Hanabi

A hand holding a stylus over a tablet covered in wireframe sketches, with a keyboard and mouse beside it. The sketches stand in for the states a component note has to name.

September 26, 2026Design systems

Documenting components so the next engineer does not guess

Component documentation should record states and the uses to avoid. A picture of the happy path leaves the next engineer guessing.

By Hanabi

A workshop where one person points at colorful sticky notes while others sit with laptops. The group is deciding together, which is the moment shared rules start to matter.

September 26, 2026Design systems

When a startup needs a design system

A startup needs a design system when a second designer or a second product would invent a parallel style. Until then, a disciplined Figma file is enough.

By Hanabi

Two white smartwatch mockups on a plain light background, one showing the face and one the back. The same object, shown twice with the same restraint, is what a shared component should feel like.

September 26, 2026Design systems

Component libraries that match the brand

A component library matches the brand when type, color, and the few repeated controls come from the product. A default kit still looks like the kit.

By Hanabi

Blue and orange ink blooming through water. The bleed of two colors is a picture of decisions that were never given separate names.

September 26, 2026Design systems

Tokens, type, and the decisions that stop visual drift

Design tokens are named decisions for color, type, and size. Visual drift starts when a screen pastes a one-off value instead of using the name.

By Hanabi

Hands typing on a laptop at a wooden desk near a window. The quiet setup fits a piece about five people keeping shared decisions in one place.

September 26, 2026Design systems

A design system for a team of five

A design system for a team of five is type, color, space, and a few shared components. Keep it small enough that the team uses it while shipping the product.

By Hanabi