Arkansas put 50 state services in one app. A letter to the director who's now being asked "why can't we?"
Dear director: someone on your board has seen the MyArkansas launch and wants to know when your residents get one app for everything. Before you put out an RFP, here's what Arkansas actually announced, what a front-door app can and can't fix, and the questions worth settling first.
On October 8, 2026, Arkansas launched MyArkansas, a mobile app built by the Department of Finance and Administration with Login.gov that gives residents access to more than 50 state services, from vehicle registration renewal to state park lodging, plus notifications about deadlines and renewals. For another agency or county, the lesson is that a single app is a front door: it helps only if sign-in, the services behind it, the web versions and the ownership of each service are sorted first. Start with a few high-volume transactions, not a list of 50.
Dear director
You've probably had the question already. Someone on your board, a council member or a deputy secretary has seen that Arkansas launched an app with more than 50 state services in it, and they'd like to know when your residents get the same.
It's a fair question, and a good instinct. Residents shouldn't need to know which department handles which form. But "one app for everything" is also the kind of idea that turns into a large contract, a long build and a launch that disappoints, if the questions behind it aren't settled first.
So before you write a scope or call a vendor, here's what Arkansas actually announced, what an app like that does and doesn't fix, and the questions we'd want answered if we were in your seat.
What Arkansas actually announced
On October 8, Governor Sarah Huckabee Sanders and the Department of Finance and Administration launched MyArkansas, an app on the Apple App Store and Google Play. The state's release describes access to more than 50 state services in one place, with more planned for future releases. It was announced at the revenue office in Springdale, and the release says it was developed in collaboration with Login.gov, the federal sign-in service.
The services the release names are the kind people actually look for: booking lodging at state parks, buying hunting and fishing licenses, renewing vehicle registration, checking real-time wait times at revenue offices, requesting vital records and applying for an Education Freedom Account. The app also sends updates and notifications about emergency preparedness, license renewals, tax deadlines and benefits eligibility.
Secretary Jim Hudson put the goal plainly: residents "do not have to search multiple websites to find the appropriate department that offers a needed service." That's the part worth borrowing. The release doesn't publish usage numbers, costs or how each service connects behind the scenes, so it's too early for anyone to say how well it works. Be careful with anyone who tells you otherwise.
An app is a front door. If the rooms behind it are a mess, residents just find the mess faster.
What a front-door app fixes, and what it doesn't
An app like this is a front door. It fixes finding: one place to start, one sign-in, one list of things you can do. It can also fix reminding, which is underrated. A notification that your registration is due next month probably prevents more frustration than any redesign.
What it doesn't fix by itself is the service behind the door. If renewing a permit online takes eleven steps today, putting a link to those eleven steps in an app doesn't make it two. If a vital records request still ends with a mailed form, the app has to say so honestly. An app is a front door. If the rooms behind it are a mess, residents just find the mess faster, and now they're finding it with your agency's name on the home screen.
That's why the useful question isn't "can we build one app?" Almost anyone can. It's "which of our services are ready to be behind it?"
Decision guide
Front door, or the rooms behind it?
| Consideration | What a one-app front door fixes | What still has to be fixed behind it |
|---|---|---|
| Finding | One place to start. | Each service's own steps and forms. |
| Signing in | One sign-in, if carried through. | Second logins inside older systems. |
| Reminding | Notifications for renewals and deadlines. | The source and accuracy of each date. |
| Support | One place to report a problem. | A named owner for every service. |
Five questions to settle before you buy anything
1. How will people sign in, and once or many times? Arkansas chose to work with Login.gov. Whatever you choose, decide whether one sign-in carries through to every service, or whether residents will hit a second login inside the app. The second option is common, and it's the thing residents notice first.
2. Which five services come first? Pick by volume and by pain: the transactions people do most often, and the ones that generate the most calls to your front desk. Five that work end to end beat fifty links. You can add more later, which Arkansas says it plans to do.
3. What does each notification promise, and who sends it? A renewal reminder is only helpful if the date is right. Decide which system is the source for each date, who checks it, and how people opt in and out. A wrong deadline sent to thousands of phones is a bad week.
4. Does the website stay just as good? Not everyone will download an app, and some residents rely on assistive technology or shared devices. Every service in the app should work as well on the web, with the same accessibility standard. Treat the app as one more way in, not the only one.
5. Who owns each service when it breaks? When the vehicle registration link fails on a Saturday, does the resident's complaint go to the app team, the motor vehicle division or the vendor that runs the payment page? Write down an owner for every service before launch. We wrote about what happens when a service request app goes offline, and the lesson carries over: the front door needs a plan for when a room is closed.
How the work moves
Before the scope gets written
- Choose sign-in
Once, across every service.
- Pick five services
By volume and calls.
- Source every date
Before any notification goes out.
- Match the web
Same services, same accessibility.
- Name owners
One per service, for weekends too.
If you're smaller than a state
Most public bodies hearing this question are cities, counties and single agencies, not governors' offices. The idea scales down, but the order matters more.
For an illustrative county, the first version might not be an app at all. It might be one clear page listing the eight things residents do most, each with a working online path, a plain note on what still needs a visit, and a sign-up for reminders. If that page gets used, you'll know what an app should hold, and you'll have cleaned up the services it will point to. If it doesn't, you've saved yourself a build.
The same thinking applies when you replace a system residents already use. When Oregon's land agency moved to a new portal, it didn't make anyone reapply for applications already in flight. Planning for the people mid-process is part of the front door too.
Sincerely, and a suggestion
None of this is an argument against what Arkansas did. Putting the state's most common transactions in one place, with reminders, is a good goal, and Secretary Hudson's point about not making people search across websites is exactly right.
Our suggestion is to answer the five questions in writing before anyone drafts a scope. Bring the answers to your board alongside the Arkansas news. It turns "why can't we?" into "here's what we'd do first," which is a better conversation for everyone.
If you'd like help working through those questions, choosing the first services, or scoping a resident app or portal that your team can actually run, that's the work our government and public sector team does. Talk to us before the scope gets written.
Related work: Sutton Place.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.