Web App Development Brisbane: Browser-Based Apps, PWAs and What to Put in the Brief

Web app development Brisbane guide: browser apps vs mobile apps vs SaaS, PWAs, stack and hosting choices, privacy basics and what to put in your brief.

Web App Development Brisbane: Browser-Based Apps, PWAs and What to Put in the Brief

Web app development Brisbane is a narrower search than it looks. The people typing it usually aren't after a brochure website, and they aren't sure they need something in the App Store. They want software that runs in a browser: a customer portal, a booking or quoting tool, a staff dashboard, a job tracker that works on a laptop in the office and a phone on site.

This guide is for Brisbane small and medium businesses weighing up that kind of build. It explains how a browser-based web app compares with a mobile app and with off-the-shelf SaaS, what a progressive web app (PWA) adds, which stack and hosting decisions actually matter to an owner, and what to write down before you ask anyone for a quote.

A note on who's writing. Adaptive Media works from Burleigh Heads on the Gold Coast, about an hour south of Brisbane. We don't have a Brisbane office. We work with Brisbane clients over video and in person when a workshop calls for it. Our commercial pages for the city are software development Brisbane and Brisbane app development. This article stays on one topic: apps that live in the browser.

What counts as a web app (and what doesn't)

A website mostly publishes information. A web app lets people do something: sign in, enter data, change a record, approve a request, see their own history. The line blurs, but a few signs tell you you're in web app territory:

If your project has most of these, the questions in this guide apply. If it's mainly pages, a blog and a contact form, you need a website, and a content management system is usually the better tool.

Typical browser-based builds we see from Brisbane and South East Queensland businesses include client portals for professional services firms, booking and enquiry tools for service businesses, internal dashboards that replace a shared spreadsheet, supplier or partner portals, and field tools for teams that work between the office and job sites.

Web app, mobile app or off-the-shelf SaaS?

Owners often arrive having already picked a format. It's worth testing that choice against the job, because each option has a different cost of ownership.

OptionBest whenWatch out for
Off-the-shelf SaaSA product already does 80% of the job and your process can bend to itPer-user fees as you grow, data export limits, features you can't change
Browser-based web appYour workflow is specific, people use a mix of laptops and phones, and you want one codebaseNeeds a plan for hosting, security updates and support after launch
Progressive web appYou want a web app that can also be installed, open full-screen and cope with patchy signalInstall and notification support still varies between browsers and devices
Native or cross-platform mobile appThe job depends on deep device features, store presence or heavy offline useSeparate release process through the app stores, and often more than one codebase

Start with SaaS if a good product exists. Paying for a subscription you can cancel is lower risk than owning code. Custom work earns its keep when the workflow is the thing that makes your business different, or when you're stitching three subscriptions and a spreadsheet together to fake one system. Our custom software development Brisbane guide goes deeper on that build-or-buy call.

Pick a browser-based app over a store-listed mobile app when most users sit at a desk for at least part of the day, when you need to share links to records, and when you'd rather ship an update once than wait on store review. Web.dev's guide to progressive web apps puts the trade-off neatly: platform-specific apps lead on device capabilities, while web apps lead on reach. Its note on platform-specific apps also points out that each update needs re-packaging, re-signing, re-approval and re-installation, whereas a web app user gets the latest version on their next visit.

Choose mobile when the app is the product your customers carry around, or when it relies on device features a browser can't reach well. If you're there, read our iOS app development Brisbane, Android app development Brisbane and Flutter app development guides instead.

Progressive web apps, explained without the jargon

A progressive web app is a web app with a few extra pieces that let it behave more like an installed app. MDN's explainer, What is a progressive web app?, describes it as an app built with web platform technologies that gives a user experience like a platform-specific app. Underneath, it's still a website running in a browser engine.

Two technical parts do most of the work:

According to MDN's Service Worker API reference, service workers only run in secure contexts, which means the app must be served over HTTPS. Any production web app should be on HTTPS anyway, so this is rarely a hurdle.

Once installed, web.dev says a PWA gets an icon on the home screen or app launcher, shows up when you search for apps on the device, opens in its own window without the browser's interface, and can work offline.

What installation looks like on real devices

This is where Brisbane owners need straight answers, because staff and customers use a mix of iPhones, Android phones and Windows or Mac laptops. MDN's guide to making PWAs installable currently describes support like this:

The practical lesson is that installation is a bonus rather than the foundation. Someone who can't install the app should still be able to use it fully in a browser tab. MDN describes this as progressive enhancement. Design for the tab first, then make installation a nice extra for the people who use the app every day.

Can a PWA go in the app stores?

Yes, as an optional extra. Web.dev notes a PWA can be listed in Google Play, the Microsoft Store and the Apple App Store, but you then have to follow each store's rules. For most internal tools and client portals, a link and a sign-in page are all the distribution you need.

When a PWA is the wrong answer

A PWA is a good default for SMB tools, but not a universal one. Look at a mobile app when the core job depends on hardware integration a browser can't offer on your users' devices, when your customers expect to find you in an app store, or when the app has to do substantial work while it's closed. Test these needs early, on the actual phones your people carry.

Stack choices an owner should understand

You don't need to choose the programming language. You do need to understand the handful of decisions that affect cost of ownership, hiring and how easily you could change providers later.

Front end. This is the part people see. Most modern web apps use a widely adopted component framework. The question to ask isn't which one is best, it's whether plenty of other developers could pick it up if your provider disappeared. Popular, well-documented tools lower that risk.

Back end and database. This holds your business rules and data. For most SMB apps a relational database is the safe default, because your data has clear relationships: customers have jobs, jobs have invoices. Ask how the data can be exported, in what format, and whether you'll have direct access to it.

Authentication. Sign-in is where many security problems start. Ask whether the app supports multi-factor authentication and single sign-on with the accounts your staff already use, and how password resets and account removal work when someone leaves. The business.gov.au cyber security checklist lists multi-factor authentication and limiting access to what each person needs among its core precautions.

Integrations. Most of the value in SMB web apps comes from not re-keying data. List every system the app must read from or write to. Ask whether each connection uses an official, documented interface, and what happens when that outside service changes.

Accessibility. A web app your customers use should work with a keyboard and a screen reader and be readable for people with low vision. The W3C's WCAG 2 overview explains that WCAG covers web applications, groups its success criteria into levels A, AA and AAA, and encourages using the latest version, which is WCAG 2.2. Writing a target such as WCAG 2.2 level AA into the brief gives everyone a testable standard.

Hosting: where the app runs and where your data lives

Hosting decisions feel technical, but three of them are really business decisions.

Managed platform or your own cloud account. A managed hosting platform takes care of servers, scaling and certificates, which suits most SMB apps. Running the app in a cloud account gives more control but needs someone to look after it. Either way, the accounts should be in your business's name, with your provider added as a user. If the hosting, domain or database sits in a developer's personal account, fix that before launch.

Where personal information is stored. If your app holds customer or staff details, find out which country the data lives in and which outside services can see it, such as email, analytics, error tracking and AI features. The OAIC's guidance on APP 8, cross-border disclosure of personal information says that before an entity covered by the Privacy Act discloses personal information to an overseas recipient, it must take reasonable steps to ensure the recipient doesn't breach the Australian Privacy Principles, and it can be accountable for what that recipient does. The guidance also explains that, in limited circumstances, giving information to an overseas cloud provider purely for storage under tight contractual control may count as a use rather than a disclosure. That's a question for your adviser, but you can only ask it if you know where the data goes.

Environments, backups and updates. You want at least a test environment and a live environment, automatic backups that someone has actually restored, and a plan for applying security updates to the framework and libraries over time. The business.gov.au checklist lists keeping software updated and backing up data among its basic precautions.

Privacy obligations for Brisbane SMBs

Whether the Privacy Act 1988 applies depends on your business, not on the app. Turnover is the first test: the OAIC's small business guidance sets the line at $3 million a year, with businesses at or below it generally outside the Act. The exceptions matter for web apps, though. A health provider, a Commonwealth contractor or a business that opts in is covered whatever its size, and so are several other categories the OAIC lists.

Covered businesses work to the 13 Australian Privacy Principles, which deal with collecting, using and disclosing personal information, keeping it accurate and letting people see what you hold about them. The Notifiable Data Breaches scheme then adds a reporting duty: if an eligible breach could cause someone serious harm, both the people affected and the OAIC must be told.

A web app usually concentrates personal information in one place, which is good for control and bad if access is loose. Building privacy in from the brief costs far less than retrofitting it. That means collecting only what you need, restricting who can see what, and logging who changed records.

What to put in a web app brief

A good brief makes quotes comparable and stops scope from drifting. It doesn't need to be long, but it should answer these questions in plain language.

  1. The problem in one paragraph. What's slow, error-prone or impossible today, and what it costs the business in time or missed work.
  2. Who uses it and from where. List each type of user, such as customers, office staff, field staff and admins, with the device they'll mostly use. Note anyone working in places with poor reception.
  3. Roles and permissions. For each user type, what they can see, create, change and approve.
  4. The three most important tasks. Describe each as steps a person takes, from opening the app to finishing the job.
  5. Install and offline needs. Say whether people need the app on their home screen, whether it must keep working without signal, and what should happen when the connection returns. This decides whether you need PWA features at all.
  6. Systems to connect. Name the products and what data moves between them, in which direction and how often.
  7. Data you'll hold. List the personal and sensitive information involved, how long you need to keep it, and any requirements about where it's stored.
  8. Sign-in and security expectations. Multi-factor authentication, single sign-on, audit logs and what happens when staff leave.
  9. Accessibility and browser support. Your WCAG target, plus the browsers and device types you must support.
  10. What you already have. Existing spreadsheets, SaaS subscriptions, brand guidelines or any half-built code.
  11. Ownership and handover. Who owns the code, domain, hosting and database accounts, and what documentation you expect at the end.
  12. Life after launch. Who fixes bugs, applies updates and adds features, and how you'll request changes.

You don't need answers to everything before the first conversation. Gaps in the brief are useful, because they show where a short discovery phase should focus. If the first release needs to be deliberately small, our MVP development Brisbane guide covers how to cut scope.

Questions to ask a web app developer

Clear, specific answers matter more than which tools a team prefers.

Working with a Gold Coast team on a Brisbane web app

Most web app work suits remote collaboration. Requirements workshops, design reviews and testing sessions run well over video, and a shared test environment means you can try each feature as it's built. Being an hour down the M1 helps when a project benefits from sitting with your staff for a day to watch how work actually happens. It's an easy trip, but it is a trip, and we'll say so rather than pretend to be around the corner.

If a Brisbane-based team matters to you for reasons beyond workshops, such as regular on-site meetings, that's a fair requirement and worth stating upfront.

Frequently asked questions

What is the difference between a web app and a website?

A website mostly presents information. A web app lets signed-in users do work, such as entering data, managing bookings, approving requests or viewing their own records. Web apps usually have user roles, changing data and connections to other systems.

Is a progressive web app the same as a mobile app?

No. A progressive web app is a web app that can also be installed, open in its own window and work offline. It runs in a browser engine and uses a single codebase. A native mobile app is built for a specific platform and usually distributed through an app store.

Can a PWA be installed on an iPhone?

Yes. MDN says that on iOS 16.4 and later, PWAs can be installed from the Share menu in Safari, Chrome, Edge, Firefox and Orion. On earlier versions, installation was only possible from Safari.

Should a Brisbane SMB build a web app or use off-the-shelf SaaS?

Use SaaS when a product already covers most of the job and your process can adapt to it. Build a web app when your workflow is distinctive, when you're combining several tools to fake one system, or when ownership of the data and the roadmap matters to the business.

Where should our web app's data be hosted?

Know which country it's stored in and which outside services can access it. If the Privacy Act covers your business, the OAIC's guidance on APP 8 sets out obligations before personal information is disclosed to an overseas recipient.

Does Adaptive Media have a Brisbane office?

No. Our team works out of Burleigh Heads, roughly an hour's drive south of Brisbane. We work with Brisbane businesses remotely and come up for workshops when a project needs it.

Sources

Official and primary pages consulted on 25 October 2026:

Next step

Write the one-paragraph problem statement and list the people who'll use the app, with the device each one reaches for. That's enough to start a useful conversation. If you'd like a second opinion on whether a web app, a PWA or an existing SaaS product is the right fit, contact us. If the answer is a subscription you can buy today, we'll tell you.