Digital licence app design system

Credentials on the Queensland Digital Licence app are designed to look and feel consistent. This helps customers using the app recognise them straight away. The Digital Licence app Design System (DLADS) enables this consistency, applying customer experience (CX) standards.

How the design system works

The DLADS defines a unified look, feel, and behaviour across all credentials. It uses reusable components, templates and patterns for a seamless and professional user experience. By following this system, we ensure that every credential aligns with the app’s design principles, reinforcing trust, usability, and accessibility.

How we created the design system

The DLADS was built through extensive co-design, customer and accessibility research, and aligned with platform-specific technical requirements. It was designed using an atomic approach to simplify the design process and reflect Queensland Government branding. It will continue evolving to meet the needs of users and uphold the highest usability and accessibility standards.

Design system features

The DLADS includes key features to support your design process:

Components

Reusable, modular UI elements that form the building blocks of the Queensland Digital Licence app. Examples include buttons, input fields, icons, and toggles. Each component is designed to be accessible, responsive, and consistent across iOS and Android platforms.

Variants

Customisable versions of components that adapt to different use cases. For example, buttons may have primary, secondary, and disabled states, each with specific styling and behaviour.

Variables

Design tokens such as colours, typography, spacing, and elevation to ensure consistency across the app. These variables align with Queensland Government branding requirements and accessibility standards.

Templates

Pre-defined layouts that provide a framework for common credential designs. Templates ensure that credentials are structured consistently and align with the app experience.

Patterns

Best-practice interaction patterns for common user tasks, such as scanning a QR code, verifying identity, or accessing credential details. Patterns are designed to be intuitive and reduce cognitive load for users.

Key principles of the design system

These principles support the DLADS:

Co-design and customer research

The system has been developed in collaboration with Queenslanders to ensure it meets their needs and expectations. Customer feedback has been central to shaping the design and functionality of the app.

Accessibility-first approach

Accessibility research has informed every aspect of the design system, ensuring that all components, patterns, and templates meet WCAG 2.1 AA standards and have been tested against native accessibility features on both iOS and Android.  This ensures the app is inclusive and usable for people of all abilities.

Platform-specific optimisation

The design system adheres to the technical requirements and best practices of both iOS and Android, ensuring customers get a native experience using the app on their platform of choice.

Queensland Government branding alignment

The design system aligns with existing Queensland Government crest branding requirements to ensure a professional and recognisable visual identity. While it is not yet fully aligned with the Queensland Government Design System (QGDS), work is underway to ensure future updates will bring the design system into compliance with QGDS standards. Additional work is scoped to add mobile app components, patterns and accessibility requirements into the QGDS, building upon the current web-based focus.

Atomic design methodology

The system uses an atomic design approach, breaking down the interface into fundamental building blocks: components, variants, variables, templates, and patterns. This ensures scalability, flexibility, and consistency across all designs and streamlines development .

Evolving documentation

The design system is supported by detailed documentation that provides guidance on its use, including information on components, patterns, and accessibility considerations. While the documentation is comprehensive and reflects the current state of the design system, it is a living resource that will continue to evolve as the system is updated and refined to align with the QGDS.

How to use the design system

1. Meet with the product manager
   Your credential is just a part of larger service integration process that includes how customers will be informed about your digital credential, how they will access it, what services will be made available with it, correspondence your customers will receive, and business and technical requirements. This process will include a kick-off meeting where these and other related topics can be unpacked.
2. Access the Figma library
   The app design system is hosted on Figma, providing you with access to all components, templates and patterns. We’ll set up your access as we work together.
3. Familiarise yourself with the documentation
   The design system includes comprehensive documentation to guide you through its use. This includes guidance on accessibility, branding and platform-specific considerations.
4. Start with templates and patterns
   Begin your wireframing process by selecting the most appropriate templates and patterns for your credential data payload and lifecycle requirements. This ensures your design aligns with the overall structure and behaviour of the app.
5. Customise using components and variants
   Use the pre-built components and their variants to create a unique yet consistent design for your credential. Ensure that any customisations align with the design system’s guidelines.
6. Test for Accessibility and Usability
   Validate your designs against accessibility standards (WCAG 2.1 AA) and usability best practices. The DLADS provides tools and resources to support this process.
7. Service integration items
   Consider other related sections with the app as required. We’ll have discussed these when you meet with the product manager. Components, templates and patterns for these are included within the DLADS.
8. Collaborate with the QDL Design System Team
   Engage with the app design system team early and often to ensure your designs meet technical and design requirements. The team can give feedback, answer questions and support you throughout the process.
9. Approval
   Each credential goes through a shared approval process, respecting the separate governance processes required by the issuing authority, and the product team. This ensures your service and credential business requirements are met, and the product, technical, security and accessibility requirements of the product are maintained.

Key considerations for credential design

• User-centred design: Always prioritise the needs and expectations of Queenslanders. Use plain language, clear labels, and intuitive navigation.
• Accessibility: Ensure your designs are inclusive and compatible with assistive technologies on iOS and Android. Test for colour contrast, keyboard navigation, and screen reader compatibility.
• Consistency: Align with the design system’s components, patterns, and branding to maintain a cohesive user experience.
• Security and privacy: Credentials in the app are used for identification and verification. Ensure your designs cater for and align with the secure and private interactions of the ISO Standard.
• Scalability: Design credentials that can adapt to future updates or changes without compromising usability or consistency.

Comprehensive design on the app

The DLADS encompasses the entire app’s user interface (UI) and user experience (UX), not just the credentials.

When designing credentials, consider their integration from a whole-of-system perspective. During the scope and design phases, you may need additional wireframes to ensure full functionality within the app.

Key considerations

• Adding a new credential to the app requires the user to verify specific attributes of their credential and provide explicit consent to share identity information between government departments. This process ensures the highest standards of trust, security and compliance with business requirements.
• Associated services relevant to the credential can be made available on the Home screen.
• Credentials that relate to high-level government campaigns can be prominently displayed on the Home screen.
• Correspondence related to the credential must be delivered to the user via the Messages feature.
• Attributes required for sharing or verifying credentials must be clearly displayed and accessible during the process.

The DLADS provides all components, templates, and patterns needed to address these considerations, ensuring consistency and alignment across the app.

Accessibility in the design system

Accessibility is a core part of the DLADS. It lets users of all abilities access and use the app with ease.

Our commitment to accessibility

• Inclusive design: All designs must be inclusive and fully compatible with assistive technologies. This includes rigorous testing for colour contrast, keyboard navigation and screen reader compatibility to ensure compliance with WCAG 2.1 AA standards.
• Collaborative research: The development of the design system was informed by targeted accessibility research conducted in collaboration with leading organisations, including Vision Australia, the Queenslanders with Disability Network (QDN), and Me2 Accessibility. Their insights were invaluable in shaping a system that prioritises accessibility at every level.
• Award-winning accessibility: The Queensland Digital Licence app was recognised for its excellence in accessibility, winning two prestigious 2025 Access Awards:
  • Government App of the Year
  • App of the Year (across both private and public sectors).

Alignment and principles

The DLADS aligns with established Queensland Government standards, policies, and principles:

• Human-Centred Design Framework: Placing the needs, behaviours, and experiences of users at the core of the design process.
• Digital Service Design Playbook: Leveraging best-practice methodologies to guide the design and delivery of effective digital services.
• Digital Services Policy: Ensuring digital initiatives align with government priorities and deliver value to Queenslanders.
• Digital Service Standard: Meeting the 13 principles that underpin the delivery of high-quality, accessible, and user-focused digital services.
• Principles for the Design, Development, and Deployment of Mobile Apps: Adhering to guidelines that ensure mobile apps are secure, reliable, and meet the expectations of Queenslanders.

Credential design approval process

To ensure credentials on the app meet the DLADS standards, all credentials go through an approval process. This process helps your design team adhere to the DLADS and ensure trust, confidence, reduced cognitive load and a cohesive customer experience.

Submit designs for review

Once your design team has wireframed its credential, share the Figma files with the internal review team. The submission should include all relevant wireframes and documentation, so the review is comprehensive.

Internal review and feedback

The review and approval process typically takes 5–10 business days, depending on the design’s complexity and the completeness of the documentation provided.

The internal review team will assess the designs to ensure they align with the DLADS and the Queensland Government’s broader design standards.

The review focuses on:

• adherence to the DLADS, including components, templates, and patterns
• compliance with accessibility standards, including compatibility with assistive technologies and WCAG 2.1 AA requirements
• consistency with the app’s customer experience (CX) standards, ensuring a unified look, feel, and behaviour
• alignment with the app’s principles of trust, usability, and reducing cognitive load for users.

The internal team will give clear, actionable feedback to your team, noting any areas needing adjustment.

Approval and handover to development

Once your wireframes are approved, they will be ready for the next phase. The designs will go to the product team’s development pipeline for implementation. This ensures that the final product not only meets design and accessibility standards but also integrates seamlessly into the app’s existing ecosystem.