Aaron Makaruk

← Work MyLowe's Home

Shipped · Lowe's · 2025 – 2026

MyLowe's Home

Designing a home management feature for the Lowe's app, iOS and Android.

Role
Lead Product Designer, Mobile
Team
Product management, iOS, Android, and backend engineering, design peers, directors, Senior VP sponsor
Years
2025 – 2026
Platforms
iOS, Android

Overview

MyLowe's Home (MLH) is a feature inside the Lowe's mobile app that gives customers a profile of their home: the products in it, the rooms they belong to, the projects underway, and the warranties and maintenance that come with all of it. It is built on the data Lowe's already holds about each customer, a property-data integration, Lowe's planning tools, and an LLM layer for guidance.

I designed the feature for iOS and Android. That included defining the information architecture, designing every screen and flow, building the interactive prototypes, running usability research, and working through implementation and QA with engineering until it shipped.

The Problem

Owning a home means keeping track of a lot: appliance manuals and warranties, the paint color in the bedroom, the flooring you're considering, the filter that needs replacing next month, the project you started and haven't finished. Most people keep this in a drawer, a photo roll, or nowhere. Lowe's was in an unusually good position to solve this. It already knew what customers had purchased, searched for, and saved. It had planning tools customers used for real projects: paint and color visualizers, flooring calculators, blinds tools, room measurement. It had how-to content and warranty data for the products it sold. None of it was connected to the customer's actual home. The job was to design a feature that turned all of that into something a customer would use to run their home, and that felt like a natural part of the Lowe's app rather than a bolt-on.

Understanding the Feature

I started by analyzing the full scope: the data Lowe's could bring to the feature, the tools that already existed, what customers were trying to do, and where MLH had to sit inside the existing app. The customer needs were concrete: know what I own and where it is; find the manual or warranty when something breaks; get reminded about maintenance before it becomes a repair; keep track of the choices I've made for each room; plan projects with real numbers and see what they'll look like; get answers without reading a manual. Underneath those needs was a simple structure. A home contains rooms. Rooms contain products. Projects touch rooms and products. Warranties, maintenance, and guides belong to products. Every screen in the feature turned out to be either a list of one of these things or the profile of one of them, all reachable from a dashboard. Settling that early gave the team a clear map to build against and gave customers one consistent way to move through the feature.

Make the First Session Valuable With Zero Effort

The feature is only useful once it knows about your home, and asking customers to enter everything by hand would kill it. So onboarding starts with an address: the app pulls property details from the ATTOM property-data API and builds the Home Profile automatically. Appliances purchased on a MyLowe's Rewards account appear on their own, with manuals and warranty details attached. Customers refine a profile that already exists instead of building one from scratch.

Make the Product Profile the Workhorse

Most day-to-day value lives here: warranty status, manuals, maintenance schedule and reminders, recommended parts and supplies, and how-to guides. I designed it so the most time-sensitive information (warranty expiring, maintenance due) surfaces first and the reference material sits below. Guides are backed by an LLM, so a customer can ask a question about their specific product in context. The design keeps this inside the Product Profile rather than as a separate chat destination, so the answer always has the product as context.

Keep Room Decisions With the Room

A Room Profile holds paint colors, flooring, measurements, and visualizer output. When a customer uses a paint visualizer or flooring calculator, the result attaches to the room. The choices made during planning stay findable long after the project is done.

Treat Projects as a Lifecycle

Customers can browse projects, save them, plan them using Lowe's calculators and visualizers, and mark them complete. Project Profiles connect out to the tools and back to the rooms and products they involve.

Give the Dashboard One Job

It answers what needs my attention right now: upcoming maintenance, expiring warranties, active projects, and quick paths into rooms, products, and projects.

Design Once, Honor Both Platforms

The feature shipped on iOS and Android with a shared structure and platform-appropriate patterns for navigation, controls, and system behaviors.

Building and Shipping

I worked directly with the iOS, Android, and backend teams across multiple quarters of sprints on feature planning, implementation, and QA. I reviewed builds continuously, tested flows on device across both platforms, logged design defects alongside functional ones, and adjusted designs when implementation surfaced constraints. When Apple provided feedback during App Review, I worked with the team to interpret it and revise the design and implementation. Throughout, I presented the work and facilitated decisions across designers, product managers, engineers, and directors, with a Senior VP sponsoring the feature.

Research and Iteration

We ran usability studies at the Lowe's Tech Hub lab in Charlotte. I flew out and participated in the sessions, testing first with interactive prototypes and later with the feature in code. We paired lab findings with product analytics to see the paths customers actually took. Revisions went into the design files, the prototypes, and the shipped code, where I worked with engineers to implement them.

Results

MLH shipped on iOS and Android and was refined across multiple release cycles with direct customer input. It gave Lowe's customers a working profile of their home and gave Lowe's a platform to keep building on.

What This Project Shows

Full ownership of a complex feature, from analysis and architecture through screens, prototypes, research, and shipped code. Designing from data and existing tools, turning what a company already has into something customers use. Cross-platform craft on iOS and Android inside a large production app. Working with engineering through the build, not just handing off. Research that changes the product, with revisions carried into the shipped feature.

Note

Lowe's, MyLowe's, and MyLowe's Home are trademarks of Lowe's Companies, Inc. Work shown for portfolio purposes.

What I’d Do Differently

Find the pattern before designing the screens. The most valuable decision was structural and made before any high-fidelity work. Design for the container, not just the content. Getting the handoff point right protected both the feature and the app around it. Stay through the build. The best decisions happened in the sprints, in QA, and in the lab.