Asking Muse to check how your company site looks on a phone
Asking Muse to check how your company site looks on a phone I'm not a developer of Sakupa. I write as someone who looks into tools I find interesting and shares what I learn from the official site and manual. Most peo
Asking Muse to check how your company site looks on a phone
I'm not a developer of Sakupa. I write as someone who looks into tools I find interesting and shares what I learn from the official site and manual.
Most people will open your company site on a phone first. A page that looks fine on a computer can feel cramped on a small screen: text too small to read, buttons too close together, a photo that pushes the menu off the screen. This post walks through how I ask Muse, my personal AI agent, to check how a Sakupa site looks on a phone β and what to do with what it finds.
Why check on a phone at all
A site is built on a computer, so it is easy to forget the phone entirely. But a customer looking up your opening hours on the way to your shop is almost certainly on a phone. If the hours are hard to find on a small screen, the site has failed at the one job that matters in that moment.
The check is not about design taste. It is about whether a visitor can read the important things and tap the important buttons without zooming in or hunting around. That is a small list, and it is easy to check one item at a time.
Decide three things before you ask
Before asking Muse, I decide three things:
- What to check
- Which pages matter most
- What not to change
What to check is a short list, for example: can the opening hours be read without zooming, are the buttons big enough to tap, does any photo push text off the screen. A short list keeps the result readable.
Which pages matter most is usually the top page, the menu or services page, and the contact page. Checking every page at once produces a long list that is hard to act on. Starting with the pages a first-time visitor opens is enough for a first pass.
What not to change is worth saying out loud: "check only, don't change the text." A check that quietly rewrites your wording is worse than no check at all.
The flow in chat
With Sakupa connected to Muse, I say something like: "Please check how my site looks on a phone, starting with the top page." I pass along the three things I decided, in my own words, so Muse has less room to guess.
Sakupa's usual flow follows: analyze reads the current state of the site, then a preview is shown before anything is executed β the two-step confirmation. The result of the check is best received as a list first:
- What is hard to read on a phone
- What is hard to tap
- What to do about each one
I look at the list first, then decide what to fix. "Fix just these two" keeps the change small. When something is fixed, it goes through the same preview-and-confirm step before deploy publishes it.
Three things to watch when checking
There are three things I keep in mind:
- Readability is the shop's call, not the agent's: whether the text is "too small" depends on who reads it. If older customers are a big part of your visitors, say so when you ask, so the check is judged against your visitors, not a generic standard.
- Fix one thing at a time: making the text bigger and moving a photo at the same time makes it hard to tell which change helped. Small requests, one at a time, keep the result clear.
- Check again after fixing: a fix can push something else off the screen. After a change, ask for the same check again on the same page before publishing.
What it costs
A site starts with a 30-day free preview. After that, only the sites you keep are billed, from Β₯200 a month per site. Asking for a phone check costs nothing extra.
Payment goes through a Stripe-hosted page only. The design does not hand your card number to the AI.
Summary
- Before asking, decide what to check, which pages matter most, and what not to change
- Ask for the check as a list first, then decide what to fix
- Say "check only" so the check does not rewrite your text
- Fix one thing at a time, and check again after each fix
- Every change still goes through preview and confirmation before it is published
I'm not a developer of Sakupa. This is based on the public information on the official site and manual. Please check the official pages for the latest pricing and features.
References
- Sakupa official site: https://sakupa.com
- Sakupa official manual: https://sakupa.com/manual
- @sakupa/mcp (npm): https://www.npmjs.com/package/@sakupa/mcp
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.