About this Project
Optim Household works alongside Optim Individual, the mobile app. Household takes care of the home network as a whole — first-time setup, troubleshooting when something breaks, and the more advanced settings — while Individual handles the everyday: quick checks and changes, right from the phone.
To most people, Wi-Fi only matters when it stops working. Optim Household is a network configuration service: the web page every home gateway has, where you change the Wi-Fi password, open a port or read the log. It is built on OpenWrt, the open-source operating system for routers. Our goal is to make it as easy and clear as possible, so a household can set it up once and get back online on its own.
Process
The following illustrates the process I went through for this project:
Define
Audited every legacy page and sorted each into redesign, restyle, keep, merge, or later.
Learn
Rebuilt the OpenWrt-style menu into eight sections, led by what a household opens first.
Design
Jul 2024 The setup wizard, then the Internet and LAN interfaces and port forwarding.
Aug Parental control.
Sep Security and the firewall.
Build
Phase one: the new look on every page, with a new Home and Topology.
Define
Learn
Design
Build
Validate
Audited every legacy page and sorted each into redesign, restyle, keep, merge, or later.
Rebuilt the OpenWrt-style menu into eight sections, led by what a household opens first.
Jul 2024 The setup wizard, then the Internet and LAN interfaces and port forwarding.
Aug Parental control.
Sep Security and the firewall.
Phase one: the new look on every page, with a new Home and Topology.
Challenges
How do you design a page people would rather never open?
Setting up the Internet takes time and some technical knowledge. When something goes wrong, most people call, reset or reboot — and for an ISP, a household coming back here usually means the Internet has a problem.
If OpenWrt already had every feature, what was left for Actiontec to do?
On Actiontec’s gateways, this page was OpenWrt’s own. Every feature was there, but the menu followed the firmware’s structure, and the first screen showed the kernel version and memory in use — what an engineer checks, not a household. What had to change wasn’t the features, but who the page was for.

Insights
Set up once. When something breaks, show where.
Setup should be done once, without help. When people open the page again, it’s usually because something is wrong — so the first thing they see should be where the problem is, and everything else can wait.
Structure follows the household, not the firmware.
The menu became eight sections, led by what a household opens first, with the pages only experts need moved to Advanced settings.
Design
What follows is the product as a household meets it: setting up, troubleshooting, changing a setting — and the header and side menu every page shares.
Setting up (wizard)
Every Wi-Fi product has a setup wizard. Whether the router is being set up for the first time or has just been reset, it helps the household get the Internet up and running quickly.
At this moment, the line is connected to the router and the router is powered on, but the Internet can’t reach the rest of the home until the router is set up. The factory password may be blank, and at the end, the Finish button restarts the very Wi-Fi the person is using.
Before any of that, onboarding checks the line. As soon as the router is online, it downloads the setup package the ISP has prepared for it. We gave ISPs an interface to offer that package, so a household on an ISP that uses it doesn’t walk through the whole wizard: the settings arrive on their own, and setup is done in a step.
Onboarding checks the line first; the ISP’s settings can be downloaded here.
Only if needed: choose how the line connects — DHCP, PPPoE or a static IP.
It opens on the ISP’s own welcome, with their logo.
Read and agree to the terms of use.
Name the Wi-Fi and set its password; a smart-home network can be added with one switch.
The router’s name and time zone, already filled in.
Set the password for the router’s page — and keep it saved.
Everything chosen, on one page, ready to copy or screenshot before anything restarts.
The router and its extenders, with two ways to pair another one — then Finish. (This step was later dropped because of a technical constraint.)
Once setup is finished, the household signs in to the router’s page with the password they just set.
Onboarding checks the line first; the ISP’s settings can be downloaded here.










After this, most households won’t need the page again.
Troubleshooting
Here’s a use case. One weekday evening, the Wi-Fi in the back room keeps dropping. Before calling the ISP, someone opens this page to see what’s wrong.
When something goes wrong, Home should make it as clear as possible at a glance — ideally, whether the problem is outside the home or inside it. Here the Internet card says Connected, so the line from the ISP is fine — the problem is inside the home. Had the Internet been down, Home would name the cause — a cable, the Internet, or the router — instead of just saying offline.

Topology shows where. The router reaches the study’s extender over Ethernet, but the AP beyond it hangs on a 2.4 GHz wireless link — most likely the weak spot. Every piece of equipment, how it connects and how fast, on one map.

When it’s slow
A week later, the same family’s evening streams keep buffering, and the first suspicion falls on the ISP. That’s common: in one survey, people blamed their provider for streaming slowdowns about as often as their own Wi-Fi — 36% against 35.9%.
Most speed tests run on a phone, over Wi-Fi, so the result mixes the room’s signal with the line itself. Optim Household runs the test from the router — Actiontec’s own equipment — straight out to the Internet, with the Wi-Fi taken out of the picture.


Here the line delivers 1030 Mbps down and 750 up, with 12 ms latency — the plan is doing its job, so the slowdown is somewhere inside the house. Every test is kept, with its date and the server it ran against, and the history exports as a file. When the family does call support, “it was slow last Tuesday night” comes with the numbers.
Changing settings
Then the teenager’s new game console reports a “strict NAT”, and a guide online says to open some ports. Opening ports isn’t something people do often, so most follow the guide field by field without knowing what each one means — and when the console still can’t connect, they can’t tell what went wrong.
So the port forwarding page makes each rule say what state it’s in — on, inactive, disabled, error or misconfigured. Instead of guessing, people can see which rule is wrong and why. The list holds up to twenty.

But a forward only works if the console keeps the same address. Reserved IP gives it one — and warns that changing the router’s own address means updating these too.

For the expert
Some problems still end in a call to support. The agent may need to see the router for themselves — but in most cases a household won’t, and shouldn’t, read out its admin password over the phone. So the page creates a temporary login for the agent, over the web or SSH. Each one shows who created it, and closes itself after fifteen minutes — nothing is left behind.

The deeper tools a technician uses — WAN types, static routes, packet capture — live in Advanced settings: out of the household’s way, and complete for the person who needs them.

The header and side menu also have to know when not to appear. When the family adds an extender and types its address into a browser out of curiosity, a full side menu of router settings would invite them to change things that should only be set on the main router.
So the extender’s page has no side menu at all — just a plain note: this unit is an extender — set up the main router first, or reset it to use it as a router.

The side menu keeps its place, too. The first version forgot where you were when you opened another group; this one keeps one group open at a time and brings you back to the level you left.

Beyond this Project
Nothing on the old page was missing. What changed is who it’s for: a household that would rather not need it.
The main design closed in early 2025; since then the work has been fixes and refinements as the pages meet development.
More screens from the design document, by part of the story:
Day one: signing in, help, loading and errors (4)
Remembering a sign-in is convenient, but it mustn’t outlive a deliberate log-out. “Remember me” starts unchecked, logging out forgets the saved password, and a failed sign-in clears the field.


Help page inside the app: accordion of topics (pairing extenders, terms and privacy).

Loading state: a clockwise spinner over the dimmed app shell.

Fallback error screen: "Something went wrong" with Back to Home.
Coming back: Home’s first release and the device list (2)
Opening one card shouldn’t make you lose the rest of the overview. Only the card you pick expands, over the grid; on a phone, its detail takes the whole screen.

People want to see at a glance which devices are online and how well they’re connected. Each row turns signal, band and speed into one coloured icon and a readable rate, and a missing value shows as a dash, not a zero.

When it’s slow: diagnostics (1)
After a diagnosis, you need to compare what you typed with what came back. The form stays filled in beside the result, each method checks its own kind of target, and leaving with unsaved edits asks first.

Changing settings: Wi-Fi names, firewall, firmware, reboot, password (5)
Splitting one network into one per band shouldn’t leave broken names. Each band’s name gets its suffix, trimmed to fit the length limit, and options that only work in some setups appear only there. Every Wi-Fi card starts open.

Some protections depend on others, and some quietly change other behaviour. The page says so beside each switch — for example, that blocking trace route also turns off pings from outside.

A firmware update, a restore or a reset can’t be undone. Each asks first and then leads straight into the reboot, and the last time server can’t be deleted, so the router never loses its clock.

A reboot cuts the connection, and people need to know what happens next. The page says up front that the Internet will be gone for a minute or two, then gives each path its own ending — including someone reaching the router from outside the home.

Changing the admin password from inside the app should follow the same rules as setup. It uses the wizard’s password rules, stays hidden until you choose to see it, and has to match its confirmation.

Advanced settings: WAN, static routing, public LAN, DDNS, capture, 802.1x, DMZ, ALG, log, UPnP (11)
Changing the connection type shouldn’t wipe what you typed or leave settings that can’t work together. Values carry over when you switch, combinations that can’t work are turned off, and saving warns that devices will drop for a few seconds.

The earlier model mixed the kind of link with how the address is set. The next release separates them — the link type comes first — drops options it won’t carry, and an unknown state says “Not configured. Set up now.”

People might read the order of the routing table as the order routes are applied. The page says plainly that it isn’t, and rules are added one at a time, newest on top.

Switching to Routing needs a complete form, and people may leave it half-filled. Switching always opens the form, and leaving it empty asks first; cancelling returns to the mode you had.

Reaching the router by name needs a Dynamic DNS record that stays current. One configuration shows its IPv4 and IPv6 result and when it was last updated; a backup WAN would one day need more than one.

A packet capture takes time, only one can run at once, and leaving the page loses it. Start stays disabled while a job runs, the status keeps updating, and the file is ready once the capture finishes or is stopped.

Ports need authentication, but the backend supports only part of the model. The page offers what works today, says what isn’t supported yet, and won’t delete a profile that’s in use.

Picking the DMZ host gets confusing with guest devices and more than one set of LAN addresses. The list leaves guests out and sorts the rest, offline hosts are labelled, and the address has to sit in the main LAN.

Protocol helpers are switched one by one, and people need to know each change worked. Every switch takes effect at once — there’s no Save — and a short message confirms it.

The log is cleared on every reboot, and people choose which severities it records. An empty log is the normal state, not an error; the log scrolls in full, exports exactly what you’re looking at, and a slider sets what gets recorded.


UPnP: a single enable toggle that applies immediately, with no Save & apply.
The frame: the first sidebar (1)
The menu holds six sections and many pages, and still has to fit a narrow rail. Hovering expands it with your page still marked, only one group opens at a time, and signing in lands you on Overview.

The frame: the captive portal (1)
The guest sign-in page is served by OpenWrt, outside the main app, so it can’t borrow the app’s styling. It keeps to plain type and two simple states: a prompt to get online, and a confirmation.
