Author

Hanabi

Page 2

A clothing shop interior with folded shirts, hanging jackets, shelves, and pendant lights. The racks are the variant problem: many sizes and colors, one product the page still has to explain.

September 26, 2026Ecommerce

Variants and inventory without a messy product page

Show the variant choice that changes the object, and hide the full matrix of combinations. Mark what is unavailable on the control instead of sending the shopper to an error.

By Hanabi

A bright office window ledge with a laptop, a closed notebook, white chairs, and a tall indoor tree. The quiet setup fits the moment after payment, when the shopper needs a clear next step.

September 26, 2026Ecommerce

The page and the email after purchase

The confirmation page and the email after purchase should say what happens next, when the order arrives, and how to ask a question. The email repeats that in plainer words.

By Hanabi

Two white smartwatch mockups on a plain light background, one showing the face and one the back. The pair shows what a consistent crop and background do for objects in a row.

September 26, 2026Ecommerce

Photography, crop, and the product grid

A product grid looks finished when the crop and the background stay consistent. Mixed crops make a shop look unfinished faster than a new typeface will repair.

By Hanabi

A clothing shop interior with folded shirts, hanging jackets, shelves, and pendant lights. A catalog this considered should be carried carefully to a new address.

September 26, 2026Ecommerce

What to migrate from WooCommerce, and what to leave

Bring products, customers you may contact, orders you must keep, and the URLs people already use. Leave the plugins that only patched the old WooCommerce theme.

By Hanabi

A close view of a smartphone home screen filled with app icons on a pale table. This is the small screen a shop has to work on.

September 26, 2026Ecommerce

Mobile shopping for a brand with a point of view

A phone shop should keep the brand’s crop, type, and a thumb path from picture to price to bag. A squeezed desktop grid is a different store, and it loses the first glance.

By Hanabi

An OPEN sign hangs in a shop window, with the word SHOP printed on the glass. The open door only matters if the counter inside is easy to finish.

September 26, 2026Ecommerce

The checkout fields that cost the sale

Fewer fields, a visible total, and a guest path are the checkout changes that protect a sale. Baymard’s research separates browsing from costs, accounts, and long forms you can fix.

By Hanabi

Two white smartwatch mockups on a plain light background, one showing the face and one the back. The object is the whole picture, which is how a product page should open.

September 26, 2026Ecommerce

Product pages that explain the thing, then step aside

Lead a product page with the object, the price, and the one reason it exists. Materials, shipping, and the longer story come after a decision is possible.

By Hanabi

September 26, 2026Ecommerce

Ecommerce design for a brand, not a marketplace

A brand shop is an edited room with a point of view, not an infinite marketplace grid. Price, trust, and the path to pay still have to be obvious.

By Hanabi

Hands typing on a laptop at a wooden desk near a window. The desk is where you time the old chore and the new review.

September 26, 2026Automation

How to tell whether an automation saved time

Time the old chore against the minutes spent reviewing the automation. If checking it takes longer than the work did, remove it.

By Hanabi

A person in a purple shirt typing on a bright blue laptop at a round table. Support automation is still a reply someone has to be willing to send.

September 26, 2026Automation

Support automation that does not sound like a script

Support automation should use the brand's real sentences and offer a person when the question leaves the script. Do not give the bot an employee name.

By Hanabi

A person gesturing in a meeting, with a laptop showing a colorful layout, a notebook, and a phone on the table. The gesture is the judgment; the laptop is one set of options.

September 26, 2026Automation

How a studio can use AI in design without handing over judgment

A model can widen design options and speed production chores. The studio still decides what is clear, what is on brand, and what ships.

By Hanabi

A hand holding a stylus over a tablet covered in wireframe sketches, with a keyboard and mouse beside it. The sketches are the screen someone was already editing, which is where an assist belongs.

September 26, 2026Automation

Adding AI without turning the product into a chat box

Put an AI assist on the field the person was already editing. A blank chat is a new product they did not open the screen to learn.

By Hanabi

Hands sketching a user-flow diagram labeled user goals on a sheet of paper. The diagram is where a team draws the line between an automatic step and a human check.

September 26, 2026Automation

Where a human still has to review the work

Keep a person on anything a customer will see, pay, or be unable to undo. Draw that review into the workflow as a real control.

By Hanabi

A workshop where one person points at colorful sticky notes while others sit with laptops. The notes are the repeated handoff; the conversation is the judgment that stays human.

September 26, 2026Automation

When a service business should add automation

Automate the repeated handoff in a service business, such as scheduling and file delivery. Leave the judgment the client is paying for with a person.

By Hanabi

Two people pointing at a laptop screen, one wearing a fitness band. They are checking the same result, which is the posture a trustworthy feature should allow.

September 26, 2026Automation

Designing an AI feature people can trust

People trust an AI feature when they can see the source, the limit, and an easy edit. A confident wrong answer, with none of those, is a defect.

By Hanabi

A person in a purple shirt typing on a bright blue laptop at a round table. The picture sits with this piece because a community bot is still someone at a keyboard, answering in a shared room.

September 26, 2026Automation

Discord bots as a product surface

A Discord bot should live where the community already talks. Design a few commands, help text, and a real way to reach a person.

By Hanabi

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