ServicesSupport and maintenance
Ongoing support and maintenance for websites, web apps, and iPhone and Mac apps: the updates, platform changes, bug fixes, and small improvements every live product needs. One team owns all of it, month after month, so none of it lands back on your desk.
What’s covered
None of this is dramatic, and that’s the point. Small, steady work keeps small problems from turning into big ones.
Dependency and security updates, applied and tested, so the code your software is built on doesn’t quietly go stale.
New browser versions, new releases of iOS and macOS, App Store requirements, and changes to the services your software depends on.
The bugs only real use turns up, fixed properly and tested so they stay fixed.
Regular attention to speed, contrast, keyboard access, and screen readers, because both drift as content and features change.
A new page, a new section, updated copy or screenshots, a tweak to a flow. The small requests that otherwise pile up.
Changes based on how people actually use it, made in small, safe steps instead of saved up for a big redesign.
How it works
Support works best as an ongoing arrangement, so there’s always someone who knows your software. It has two parts, and we agree on the details up front, based on what your software actually needs.
Part one
The routine work that keeps everything current, done on a schedule, so it never waits for something to break.
Part two
Time set aside each month for whatever comes up, without starting a new project every time.
We decide together what’s included and how requests reach us, so nobody is guessing later.
A new feature or a redesign gets its own plan and estimate, so it doesn’t quietly use up the time set aside for upkeep.
Nobody can honestly promise that. What you get is a team that knows your software and has time reserved for it.
Proof
Our products keep changing after launch. A few of the changes we’ve made since:
After launch, the feedback was about trust, so files are now encrypted before upload and the service never holds the key.
After we looked at the site the way its visitors see it.
Along with configurable toolbar actions and custom shortcuts, in the live extension.
The new theme switch reads the old one’s saved setting, so nobody’s light or dark pick was lost.
Google Analytics runs with advertising features, Google signals, and User-ID disabled.
When the old service pages were retired, each address kept sending people somewhere useful.
Websites, web apps, and native apps
Browser releases, dependency and security updates, forms and integrations that need checking, content and design changes, and a regular look at speed and accessibility.
More on websitesFramework and library upgrades, changes to cloud services and APIs, the bugs real use turns up, and small features as the product grows.
More on web appsEach new iOS and macOS, deprecated APIs, App Store requirements and privacy disclosures, and new devices to support.
More on iPhone and Mac appsGood fit
It’s most useful once your software is live and something you depend on, whoever built it.
From the blog
Browser support is not a default engineering checklist. It is a product decision shaped by your audience, requirements, and the cost of compatibility.
Brave blocked over a hundred tracking requests on a site where we had installed exactly two analytics tools. Figuring out why changed how we choose analytics.
Before you ask
No. If someone else built it, we start by getting to know it (that’s taking over existing software), then look after it like anything we built ourselves.
Recurring maintenance (updates, platform changes, and keeping builds and deploys working) plus reserved capacity for fixes, small design and content changes, and improvements. We agree on the specifics up front, based on what your software needs.
No, and we’d be wary of anyone who says theirs is. Time is set aside for you, and bigger work, like a new feature or a redesign, is scoped and agreed on its own.
Urgent problems come first. How they reach us and how we handle them is something we agree on before anything goes wrong, so nobody is working it out in the middle of an outage.
Yes. We’ll hand everything over with documentation, so your team, or whoever comes next, can pick it up without guessing.
Contact
Tell us what you have and what it needs. We’ll get back to you as soon as possible.