Mobile App Development Company in Canberra

Two questions set a Canberra app budget: which classification the data plane sits at, and whether citizens or staff are the users. A scoped mobile MVP for an ACT Government or federal department workforce app (Flutter or React Native, single platform, OFFICIAL-equivalent data plane, basic Microsoft Entra ID integration) runs twelve to twenty weeks; a native iOS plus Android citizen-facing app with myGovID or Australian Government Digital ID integration, full accessibility audit, Digital Service Standard alignment artefact pack, and Privacy Impact Assessment runs twenty to thirty-six weeks. PROTECTED-classified data plane work delivered alongside an IRAP Assessor adds advisory and rework cycles, and Defence Connect-adjacent work requiring DISP Level 2 partnerships ranges higher. Canberra rates sit above Adelaide and Brisbane because of procurement compliance overhead and AGSVA personnel scarcity. Codazz quotes fixed-fee on agreed scope with progress payments tied to acceptance, not open T&M with surprise variations.

The Digital Service Standard (DSS) is the Digital Transformation Agency's standard for designing and delivering government digital services in Australia. It has thirteen criteria covering user research, accessibility, content design, security, technology choices, performance measurement, and continuous improvement. Federal entities building citizen-facing or staff-facing services are expected to align with the DSS, and major projects undergo formal DSS assessments at alpha, beta, and live phase gates. Our DSS-aligned engagements deliver user research artefacts (recruited through Hotjar, UserTesting, or direct recruitment depending on cohort sensitivity), WCAG 2.1 AA accessibility audits with remediation tracking through to formal accessibility statement issuance, plain language content reviewed against the Australian Government Style Manual, security posture aligned with the ISM and Essential Eight, and a continuous improvement playbook the product owner can run after handover.

Accessibility is a hard requirement, not a polish layer. WCAG 2.1 AA is the federal floor under the DSS, the Disability Discrimination Act 1992, and the National Disability Strategy 2021-31. We embed accessibility from design — colour contrast verified in Figma, semantic structure planned before code, keyboard navigation patterns mapped, screen reader narratives drafted for every flow. Implementation uses VoiceOver and TalkBack from day one, with automated checks through axe DevTools, Accessibility Inspector (iOS), and Accessibility Scanner (Android) running in CI. Manual audits are conducted by Intopia, Centre for Inclusive Design, or another qualified accessibility consultant before any user acceptance testing. The accessibility statement issued at launch lists residual non-conformances with remediation timelines — we will not ship an app claiming AA conformance when it does not meet the standard, even under deadline pressure.

Yes. myGovID is the federal identity provider for accessing government services, currently transitioning to Australian Government Digital ID under the Digital ID Act 2024 administered by the Digital Transformation Agency. We integrate through OAuth 2.0 and OpenID Connect against the DTA's identity exchange, handle the assurance levels (Identity Proofing Levels 1 through 3), and design fallback flows for citizens who do not hold a Digital ID or are mid-onboarding (still a meaningful cohort — DVA, DSS, and Centrelink audiences in particular). For workforce apps inside federal departments, identity flows through Microsoft Entra ID with Conditional Access policies aligned with the department's ICT security policy. For ACT Government apps, identity flows through the ACT Digital Account where applicable, or department-specific identity for older directorates.

We handle the design, architecture, and engineering layers for PROTECTED workloads, with the data plane staying inside the client's accredited Azure Australia Central environment or sovereign-cleared alternative (Vault Cloud, Macquarie Government). The IRAP assessment is run by an ACSC-listed IRAP Assessor — we are not assessors. AGSVA-cleared personnel handle any PROTECTED-classified data inputs, typically client staff or a DISP-cleared partner firm we work alongside. We do not handle SECRET or TOP SECRET data on uncleared infrastructure under any circumstances — defence-classified work above PROTECTED is referred to DISP Level 3 partners. This boundary is documented in engagement scoping and reviewed by the client's security officer before work starts, and we pause rather than risk an unauthorised disclosure.

A native iOS plus Android citizen-facing app with full DSS alignment, accessibility audit, Privacy Impact Assessment, and myGovID integration typically takes twenty-eight to forty-four weeks from contract execution to App Store and Google Play release. Weeks 1 to 6 are discovery, user research, DSS alpha assessment preparation, classification review, and procurement pathway. Weeks 7 to 14 are design, accessibility-first prototyping, content design, and DSS beta phase. Weeks 15 to 32 are build, with shows every fortnight to the product owner and SRO. Weeks 33 to 38 are accessibility audit, Privacy Impact Assessment, security review (and IRAP if PROTECTED data plane is in scope), penetration testing, and DSS live phase prep. Weeks 39 to 44 are App Store and Google Play submission, with the typical two to four weeks of review cycles. Faster timelines are achievable for ACT Government or single-platform Flutter MVPs — sixteen to twenty-four weeks is realistic if procurement and DSS expectations are scoped accordingly.

Yes. The Department of Social Services, Department of Home Affairs, Services Australia, and the Department of Health all run programs targeting culturally and linguistically diverse (CALD) Australians. Mobile apps in these portfolios commonly support Arabic, Vietnamese, Simplified and Traditional Chinese (Mandarin and Cantonese), Korean, Greek, Italian, Tagalog, Punjabi, Hindi, Dari, Persian, and Tamil at minimum, with content prioritised based on the relevant cohort's settlement data. Our localisation approach uses native iOS Localizable.strings, Android string resources, and ICU MessageFormat for plural and gender rules, with right-to-left layout support for Arabic, Persian, and Dari. Translation is handled by NAATI-certified translators (the AUSIT and TIS National panels) rather than machine translation for any user-facing copy, with back-translation review for terms-of-art and benefit-determining language.

Codazz can engage through the BuyICT and DTA Digital Marketplace pathways for federal procurement where the buyer prefers panel-based engagement. Common SoW pathways include the Digital Sourcing Network (DSN), DTA's Software Marketplace, the Software Innovation Panel, and the Cloud Marketplace for hosting decisions. For ACT Government, the ACT Government Procurement Solutions panels apply. We do not currently hold pre-qualified positions on every panel, so engagement timelines for first-time work include panel onboarding (typically four to twelve weeks). For accelerated procurement under the Commonwealth Procurement Rules' approach to limited tender, urgent works can be scoped directly with appropriate justification, though departments typically prefer panel sourcing for governance reasons.