Web application development

A web app development company that hands you the code and the accounts

Customer portals, staff dashboards and subscription products that run in a browser, with the sign-in, hosting and accessibility decisions written down before the build starts.

Get your web app scoped in writing
Trusted by the world's fastest-growing brands

What a web app is

Software people sign in to from any browser

Web app development is the work of building software that runs in a browser: people sign in, see only what their role allows, and work with live data. It differs from a website in that the page changes depending on who is looking and what they do.

sampleharbor.test/homeProperty manager4BKitchen sink leakNew12AHeating not workingApproved214rental unitssampleharbor.test/homeTenantKitchen sink leakNew

People and roles

Before any screen is drawn we list who signs in, what each role can see and change, and how a new person gets access or loses it.

Data and hosting

We choose the database, the hosting and the way the app talks to your other systems, then explain the choice in terms your next hire can read.

Open to everyone

Screens are built to WCAG 2.2 AA from the first prototype, with keyboard use and screen readers tested as part of the work.

Browser or phone

A web app, or an app in the stores

Both are real software. The choice follows from who uses it and what it has to reach on the device.

Store appInstalled from an app storeWeb appRuns in the browser
How people get itA download from the App Store or Google PlayA link and a sign-in, on a laptop, tablet or phone
Releasing a changeSubmitted to the store, then updated by each userPublished to the server, available at the next page load
Phone hardwareDeeper access to sensors, Bluetooth and background workCamera, location and notifications, within browser limits
Code to maintainOne or two codebases, plus the store listingsOne codebase for laptops, tablets and phones
Best whenThe product depends on the device itselfStaff, customers or partners work at a desk or on the move
How we decide

We ask what the app must do on the device. If a browser can do it, we build for the browser and say so in the scope. If it cannot, we tell you before you spend $25,000 on the wrong kind of app.

Web apps in 2026

Four standards that shape a web app

Sign-in, passwords, accessibility and the legal position. Sources under each.

  1. Sign-inOWASP

    Authentication failures are seventh on OWASP’s 2025 list of web application risks.

    OWASP’s Top 10:2025 lists authentication failures as A07, covering weak password handling and sessions that outlive the sign-in. We settle how people sign in, how a session ends and how access is removed during scoping, and write each into the test plan.

  2. PasswordsNIST

    NIST sets a 15-character minimum for passwords used alone and drops composition rules.

    NIST’s current digital identity guidelines say a password used as the only factor must be at least 15 characters, and that services must not demand mixtures of character types. It is federal guidance, not a law for private apps. We use it as the starting point for sign-in rules.

  3. AccessibilityW3C

    WCAG 2.2 adds a 24-pixel minimum for tap targets and a rule against sign-in puzzles.

    WCAG 2.2, a W3C Recommendation, asks for pointer targets of at least 24 by 24 CSS pixels (2.5.8) and no step in sign-in that relies on remembering or solving something unless an alternative exists (3.3.8). Both are Level AA, the level we build to.

  4. The lawDOJ

    The Justice Department says the ADA applies to web content and has set no technical standard.

    DOJ’s web guidance says ADA requirements apply to goods and services offered on the web, and that it has no regulation setting detailed standards. The guidance names WCAG as helpful. Plaintiffs and courts commonly use it as the yardstick, which is why we build to it.

What we build

A web app in six parts, and what each one produces

Each part ends in something you can open, test and keep.

Tenant portalSigned in · TenantHomeRentDocumentsWhat needs fixingPlumbingHeatingApplianceDescribe itKitchen sink drips under the cabinet.sink-leak.jpgUploadedSend request

Customer and partner portals

One place where customers, tenants or vendors sign in to see their own records, pay, upload documents and open requests, instead of emailing your staff. You receive: the portal, the role list and a test account for each role.

OrdersInvoicesRequests
Roles and permissionsTests passingTenantOwnerManagerVendorVendors see only the jobs assigned to themWork ordersNoneOwnAllJob photosNoneOwnAllTenant ledgerOwnAllLeasesOwnAll

Roles and permissions

A table of who signs in, what each person can see, and which records each can change, agreed with you before the screens are built. You receive: the access model as a document and the tests that check it.

Sign-in settingsConfiguredStaff · single sign-onMicrosoft Entra IDConnectedGoogle WorkspaceOptionCustomers · email and passwordMinimum length15 charactersSecond stepOne-time code

Sign-in and accounts

Sign-in through the system your people already use, such as Google Workspace or Microsoft Entra ID, or email and password with a second step for customers. You receive: the sign-in setup and the steps to add or remove a person.

Request traceRefused on the serverPOST/api/units/4B/chargesTenantRead the sessionResolve role: TenantCheck: post a chargeLedger write: not run

Checks on the server

Permission checks made where the data lives, so a hidden button is never the only thing standing between a user and a record. You receive: the list of protected actions and the test results for each.

Installable web appFrom the browserInstall appSample Harborsampleharbor.testCancelInstallWhat works offlineToday’s jobsSavedJob detailsSavedUpload photosNeeds signalUpdate a jobNeeds signal

Installable web apps

A web app that can be added to a phone’s home screen and keeps working through short drops in signal, for crews and customers on the move. You receive: the app, the list of what works offline and a browser and device test log.

Signed in as Tenant, Unit 4B · own lease 2187You don’t have access to this leaseChecked on the server for your accountOther tenantRefusedOld sessionRefusedOutside roleRefused

Security testing

Test accounts try to open a neighbor’s record by editing the address in the browser, reuse a session after sign-out and ask the server for an action their role does not allow. The attempts run against the finished app before real data goes in. You receive: the attempt log, the results and what was fixed.

How it runs

Scope, design, build, launch

The next stage does not begin until you sign off on the one before it.

roles.csv

Roles and first milestone

Sample · Sample Harbor Property Management portal
RoleCan doFirst milestone
TenantPay rent, request repairs, see own leaseYes
OwnerSee statements for own propertiesYes
Property managerApprove repairs, post chargesYes
VendorSee and update assigned jobsYes
ApplicantApply online and upload documentsLater
Deferred items are listed in the same detail as the included ones.

Our stack

The tools behind the web app

What a web app is designed, built, hosted and tested with. Pick one for the detail.

Figma
Why Figma

Figma is a design tool for drawing screens and linking them into a prototype.

How we use it

We draw the sign-in, the empty states and the error messages along with the main screens, since those are where users get stuck. You comment on the prototype in Figma and approve it before any code is written.

Real-timeDev handoffTokens
FigmaYes
SketchSome
Static mockupsNo

Questions

Web app development, answered

Start here

Get your web app scoped in writing

Tell us who will sign in and what each of them needs to get done. You’ll get a written scope with the roles, the screens in the first milestone and the price for it.