User Journeys
Map each user type's path through the application — from entry point to core action to outcome. User journeys expose feature gaps and access requirements before build begins.
What Application & Platform Publishing Covers
Application and platform publishing enquiries cover the full range of software environments where users interact with digital products through a browser, device or networked interface.
This includes web applications built around specific user tasks, business platforms that support operational workflows, portals that aggregate information or services, dashboards that surface data or status, customer tools that support service delivery, and digital product environments that combine multiple functions into a single experience.
Publishing any of these responsibly requires scoping the user journey, defining feature groups, planning data flows, agreeing access expectations, clarifying integration needs and documenting support routes before release.
What Application Publishing Should Be Scoped Around
Before publishing an application or platform, these scope areas should be defined and agreed.
Feature Groups
Group features by priority, user type and dependency. Not every feature is equal — core features, secondary features and future features should be separated clearly.
Screen Planning
Define the key screens or views the application requires, what each displays, what inputs it accepts and how it connects to other screens.
Data Flows
Identify what data the application collects, processes, displays and stores — and who is responsible for each part of that data lifecycle.
Access Expectations
Define user roles, access levels, authentication requirements and session behaviour — including what happens when access is revoked or a user account is closed.
Integration Requirements
Identify third-party services, APIs, databases or tools the application depends on — including the implications if those integrations change, fail or become unavailable.
Support Routes
Define how users can report problems, request access changes or escalate issues — and what response expectations are realistic and appropriate for the product.
Key Publishing Considerations
Application and platform publishing decisions that should be resolved before launch.
- Hosting responsibility: Who is responsible for the hosting environment, uptime, performance and maintenance?
- Data privacy obligations: Does the application collect personal data? What privacy obligations apply and who is responsible for compliance?
- Authentication and access control: How do users log in, manage accounts and recover access? What prevents unauthorised access?
- Content moderation: If the platform allows user-generated content, who is responsible for reviewing, moderating and removing it?
- Version and update management: How will updates be released, communicated and rolled back if needed?
- Usage terms and limitations: What can users do with the platform? What is explicitly not permitted and how are limits enforced?
- Intellectual property: Who owns the application code, designs, content and data? What licences apply?
- Third-party dependencies: What happens if an integrated API, payment provider or authentication service changes their terms or becomes unavailable?
- Performance expectations: What load should the application support? Are there explicit performance targets and what happens if they are not met?
- Browser and device support: Which browsers, devices and screen sizes must the application support?
- Accessibility: What accessibility standards apply? How are users with specific needs supported?
- Legal pages: Privacy policy, terms and conditions, cookie policy and acceptable use policy — all may be required before launch.
- Launch communication: How will the application be announced, documented and explained to initial users?
- Incident response: What happens if the application has a security incident, data breach or significant failure?
Types of Applications in Scope
Software publishing enquiries are accepted for these application types and environments.
Customer-Facing Web Apps
Applications accessed by external customers — booking systems, account portals, service dashboards, subscription tools and product configurators.
Internal Business Platforms
Platforms used by teams or organisations internally — HR systems, project management tools, approval workflows, internal directories and resource planners.
B2B Service Environments
Platforms designed for business-to-business use — client portals, partner dashboards, API management interfaces and wholesale ordering systems.
Data & Reporting Dashboards
Interfaces that visualise, summarise or surface data from underlying systems — for monitoring, reporting or decision-making purposes.
Directory & Listing Platforms
Searchable, browsable environments that aggregate and present structured information — service directories, product catalogues and knowledge bases.
Multi-Tenant SaaS Concepts
Software concepts where multiple organisations or user groups each have isolated access to a shared platform environment.
Application scope
Applications scoped around journeys and access
Web apps, portals and business platforms are reviewed around user journeys, feature groups, screens, data flows and the access each user type needs.
- User journeys and role-based access
- Screens, feature groups and workflows
- Data flows and integration points
- Support routes after launch
Platform structure
Platform layers discussed before build
Interface, application, service, data and infrastructure responsibilities are separated out so each layer has a clear owner and expectation.
Planning an application or platform publishing project?
Start a structured software publishing enquiry covering your product type, user groups, features and launch expectations.