Building a Corporate Mobile App Catalog with AirWatch

A well-designed mobile app catalogue gives employees a clear, trusted place to find the software they need for work. With AirWatch, now associated with VMware, an organisation can manage approved applications, distribute them to corporate-owned devices, and support BYOD without relying on informal links or unmanaged downloads.

For Australian businesses, the catalogue also provides a practical way to balance productivity with privacy and security. A workforce spread across Sydney, Melbourne, Brisbane, Perth or regional locations may use different devices, networks and operating systems. A centralised catalogue helps IT teams apply consistent rules while giving staff a straightforward mobile experience.

Define The Catalogue’s Purpose

Start by deciding what the catalogue must achieve. It may provide access to Microsoft 365, field-service tools, expense systems, customer relationship platforms, secure messaging, or industry-specific applications. Each app should have a business owner, a support contact, a defined audience and a reason for being available.

Separate essential applications from optional software. Core apps might be assigned automatically to finance staff, warehouse teams or executives, while optional tools can be published for employees to install when required. This reduces clutter and helps people find the right application quickly.

Consider the working conditions of Australian users. A construction employee in Western Australia may need offline access and a rugged Android device, while an office worker in Melbourne may use an iPhone on a corporate Wi-Fi network. The catalogue should accommodate both scenarios through clear categories, device requirements and installation guidance.

Prepare The Application Inventory

Create an inventory before configuring the service. Record the application name, publisher, version, platform, licensing model, data classification, installation method and ownership details. Include internal applications, public app-store software, web shortcuts and mobile versions of existing desktop tools.

AirWatch can support different deployment approaches, including managed public applications, internal applications and applications hosted in private repositories. Internal apps may include a custom delivery driver tool or a health-service application developed for a particular organisation. Public apps still require assessment because their permissions, update behaviour and data practices can change.

Review licensing and commercial terms early. Some vendors charge by user, device, transaction or active account. The catalogue should not expose an app to thousands of employees if the business has purchased only a limited number of licences. Connect catalogue entries with procurement records and nominate someone to review renewal dates.

Organise Categories And User Access

A catalogue works best when its structure reflects how employees work. Useful categories include Communication, Productivity, Sales, Finance, Field Operations, Security and Learning. Use plain descriptions rather than technical language, and state whether an app is mandatory, recommended or available by request.

AirWatch allows administrators to use smart groups, enrolment profiles and ownership information to target applications. A sales application can be offered to customer-facing teams, while a maintenance app can be restricted to technicians with compatible tablets. Access can also be shaped by operating system, user role, location or compliance status.

Keep the employee experience consistent. Each listing should include the app icon, a short purpose statement, support instructions, privacy notes and any required permissions. If an app handles personal information, explain why access is needed and who can view the data. This is especially important for BYOD users who may worry about the boundary between workplace management and personal content.

Apply Security And Compliance Controls

Security controls should be built into the catalogue rather than added after deployment. Require approved applications to come from trusted sources, use application-level controls where appropriate, and block or remove software that creates unacceptable risks. Compliance rules can prevent access to corporate resources when a device is jailbroken, rooted, encrypted incorrectly or running an unsupported operating system.

Australian organisations should consider the Privacy Act and the Australian Privacy Principles when selecting mobile applications. An app that collects location, contacts, photos or device identifiers may create obligations around notice, consent, retention and disclosure. Businesses working in healthcare, finance or government may also face sector-specific requirements and contractual controls.

Use authentication and conditional access to protect sensitive services. Single sign-on can reduce password reuse, while multifactor authentication adds a stronger identity check. For personally owned devices, application-level management can help protect company files without giving the organisation unnecessary control over personal photos, messages or unrelated applications.

Catalogue element Recommended approach Operational benefit
Application source Use managed public apps or signed internal packages Reduces tampering and unapproved downloads
User targeting Apply smart groups by role, device and location Delivers relevant software to the right people
Access control Combine SSO, multifactor authentication and compliance rules Protects business systems from risky devices
App information Show purpose, permissions, owner and support details Helps employees make informed choices
Lifecycle management Review versions, licences and retirement dates Keeps the catalogue accurate and supportable

Configure AirWatch For Deployment

In the AirWatch console, begin by adding applications to the appropriate management area and defining deployment settings. Choose whether each app is automatically installed, available for on-demand installation, or restricted to administrators. Set minimum operating system versions and identify whether the app should be removed when the device is unenrolled.

Use assignment groups to create a controlled rollout. A pilot group might include service-desk staff and representatives from Sydney and Brisbane before the application reaches the wider organisation. This approach exposes compatibility issues, confusing permissions and network problems while the audience is still small.

For internal applications, test the package carefully on supported iOS and Android versions. Check signing certificates, installation behaviour, update paths and uninstall rules. If a mobile app requires a VPN, secure gateway or certificate, include those dependencies in the deployment design so users receive a complete working service rather than an isolated icon.

Test The Employee Experience

Technical installation is only one part of a successful catalogue. Test the complete employee journey: enrolment, authentication, app discovery, installation, update, sign-in and removal. Confirm that users can understand the listing without needing to contact IT for basic instructions.

Test on the devices people actually use. Australian organisations may have a mixture of recent iPhones, older Android handsets, tablets used in warehouses and devices operating over slower regional connections. Check performance on mobile data as well as office Wi-Fi, and verify that large downloads do not create avoidable costs.

Invite a small pilot group to report issues through a defined support channel. Ask whether categories are logical, descriptions are accurate and permissions are understandable. Test accessibility features such as text scaling, screen readers and adequate colour contrast. A catalogue that works for a broad workforce is more valuable than one optimised for a single model of phone.

Govern Updates And App Retirement

A catalogue requires continuous ownership. Assign an application manager to review security advisories, supplier changes, licence usage and employee feedback. Establish a review cycle for high-risk applications and a less frequent schedule for stable, low-risk tools.

Updates should be tested before broad release when they affect authentication, data handling or device compatibility. AirWatch can support staged deployments so an update reaches a pilot group first and then expands after monitoring. Keep a rollback plan for internal applications and record the previous version where possible.

Retire software that is no longer supported, duplicated by another service or no longer aligned with business needs. Notify users before removal and provide an approved replacement. If procurement is assessing a consumer-facing or promotional application, it should pass the same review as every other listing; even material such as Keno bonus information may require careful treatment when it relates to gambling, advertising or employee access policies.

Recommendations For A Stronger Catalogue

The following practices help keep the service useful as the organisation grows. They combine technical controls with clear communication, which is essential when employees have different levels of digital confidence.

A short catalogue is often more effective than a crowded one. Remove duplicate tools, outdated versions and applications that employees cannot use without extra infrastructure. Regularly review feedback from frontline teams, remote workers and managers so the catalogue reflects real business requirements rather than assumptions made by the IT department.

AirWatch can provide the management foundation for a secure mobile app catalogue, but the outcome depends on disciplined governance, sensible categorisation and ongoing testing. Organisations can begin with a limited pilot, refine their policies, and expand towards a complete enterprise mobility service. Explore the platform’s 30-day free trial or speak with the AirWatch sales team to start building a catalogue suited to your Australian workforce.