Apps for public sector and civic projects

Civic and public sector software built for residents rather than institutions. What our price means for procurement, and where our limits are.

The App14 team1 min read
Residents seated at a community meeting in a local town hall
Photo: Pexels

Most civic technology is built for the institution. The ones that work are built for the person standing next to the problem.

Case studyEnte Ward: civic technology at ward levelDescribed by a sitting minister as the start of something in the civic space.

Why our price matters in this sector

Public procurement is slow largely in proportion to spend. A sprint typically sits below the thresholds that trigger the heaviest parts of the process, which can remove months from a project timeline.

That is often more valuable than the saving itself, particularly for pilots. A department can prove something works, with real users, before committing to a procurement cycle for the full thing.

What we build

  • Issue reporting and caseworkResidents raising things where they are, reaching whoever is responsible for that area.
  • Service accessBookings, applications, and status, without a phone call.
  • Internal tools for small teamsReplacing spreadsheets that three people maintain by hand.
  • Pilots before procurementA real, usable version to test an assumption before a large commitment.

The constraints that matter here

It has to work for everyone. Old phones, poor connections, low confidence with technology, and people who will use it once. That constraint rules out most of what makes a product demo impressive, and leaves the part that matters.

Accessibility is not optional. Contrast, text size, screen reader support, and keyboard operation are design requirements, not an audit at the end.

Data protection scrutiny is higher. Expect to answer where the data lives and who can reach it. Our answers.

Transparency. You will need to explain the decision publicly. A published fixed price and a written scope make that a great deal easier than a quote range.

Common questions

Can a small studio work with public sector bodies?

Yes, and our price is often the reason it is possible. A sprint typically sits below the thresholds that trigger the heaviest parts of formal procurement, which removes months from the process.

Do you have public sector experience?

Yes. Our civic work includes Ente Ward, a ward-level issue reporting app, which a minister in the Government of Kerala publicly described as a unique achievement in the civic space.

What about accessibility requirements?

Public sector software has to work for everyone, including people on old devices and poor connections. We treat that as a design constraint from day one rather than an audit at the end.

Working on a civic project?

Tell us what you're trying to build and we'll tell you honestly whether a 14-day sprint is the right way to do it.

Free. No commitment. Just a conversation.

About the author

The App14 team · Design and engineering, Appetite Studio

App14 is the 14-day app sprint run by Appetite Studio, a London-registered design and engineering studio. We design, build, and ship production iOS and Android apps in two weeks, at a published fixed price. Everything we write here comes out of work we have actually delivered: the prices are our real prices, the timelines are our real timelines, and the limits are the ones we genuinely hold to.

Our articles are drafted with AI assistance and reviewed by the App14 team before publication. The prices, timelines, delivery record, and client outcomes described are our own.

Read next