Skip to main content
VC-Virtual Communications Limited

Web & Mobile Applications

Access your business systems wherever work happens

VC develops responsive web applications and connected mobile functionality. Staff get secure, role-based access to your CRM and business systems, whether they’re at a desk or on the move.

Illustration of a device ecosystem. A browser window used by an administrator, a tablet used by a manager and a phone used by a member of staff all connect to one shared API, which applies permissions and connects to the central platform or CRM and its database.

Web applications

Business systems in the browser

A web application runs in a web browser, so users don’t need to install software. VC develops web applications for:

  • Browser-based access to business systems from any supported device.

  • Responsive design that adapts to desktop, laptop, tablet and phone screens.

  • Internal systems that support day-to-day operations.

  • Management dashboards that give leaders a clear view of activity and performance.

  • Staff tools built around specific tasks and workflows.

Mobile connectivity

Connecting mobile applications to your platform

Mobile applications are most useful when they work with the same information as the rest of the business. VC’s work covers mobile application API connectivity and CRM database integration.

Mobile appAPICRM / platformDatabase

Example request flow: the mobile application sends a request to the API; the API checks the user’s permissions; it then retrieves or updates information in the platform or CRM, which reads or writes the database; the result returns through the API to the mobile application, limited to what the user is permitted to see.

The mobile application sends requests through the API. The API checks the user’s permissions, retrieves or updates information in the central platform and database, and returns the result. Everyone works from the same up-to-date information.

Security

Protecting information in transit

Information moving between a device and your systems needs protecting. At a high level, that means encrypted connections, authenticated users and APIs that only return what each user is permitted to see.
  • Encrypted connections

    Protecting information as it travels between a device and your systems.

  • Authenticated users

    People sign in, so the system knows who is making each request.

  • Permission-aware APIs

    APIs only return what each user is permitted to see.

VC’s work includes secure data transmission between mobile applications and CRM systems. Specific security measures are designed and tested for each application.

Access

The right access for each user

Different people need different levels of access:
  • Administrators can manage settings, users and permissions.

  • Managers can see their team’s work, reports and approvals.

  • Staff can see and update the tasks, projects and client information relevant to their role.

VC develops administrative and staff-level permissions and applies them consistently across web and mobile, so access is controlled wherever the system is used.

Example role permissionsExample data

Administrators

  • Manage settings
  • Manage users
  • Manage permissions
  • Same permissions on web and mobile

Managers

  • See their team’s work
  • View reports
  • Approve work
  • Same permissions on web and mobile

Staff

  • See and update relevant tasks
  • See and update relevant projects
  • See and update relevant client information
  • Same permissions on web and mobile

Cross-platform

A consistent experience across devices

When web and mobile interfaces draw on the same platform, API and permissions, users get a consistent experience. A task updated on a phone appears straight away in the web application, and the same rules apply in both.

VC carries out integration testing between CRM modules and frontend interfaces to confirm this works as intended.

Example: Task 14 is marked complete on a phone, and the same change appears in the web application, because both use the same platform and API.
Example data

Examples

What staff can do on the move

Staff access

Sign in securely and see what’s relevant to their role.

Task updates

View, update and complete tasks.

Project information

Check the status and details of projects.

Client information

Look up client details and history.

Reporting

View key figures and summaries.

Workflow activity

See what’s been assigned, approved or completed.

FAQ

Web & mobile application questions

Which approach suits a project depends on how and where people will use it, and is normally considered during discovery.
Can mobile apps connect to CRM?

Yes. Mobile application API connectivity and CRM database integration are part of VC’s documented work. The mobile application connects through an API that applies each user’s permissions and exchanges information securely with the CRM.

What’s the difference between a web app and a mobile app?

A web application runs in a browser and can be designed to work well on phones and tablets as well as desktops. A mobile application is installed on the device and connects to business systems through an API. Which approach suits a project depends on how and where people will use it, and would normally be considered during discovery.

Can different users see different information?

Yes. Role-based access means administrators, managers and staff can each have permissions suited to their role, applied consistently on web and mobile.

Will the mobile and web versions stay in sync?

When both use the same platform and API, they work from the same information, so changes made in one are reflected in the other. This is confirmed through integration testing.

How are user permissions decided?

Permissions are usually defined during the design stage, based on the roles people hold and the information and actions each role needs. For example, an administrator may manage users and settings, a manager may view team activity and approve work, and a member of staff may see and update the tasks and records assigned to them.

A common starting point is to list the main roles in the organisation, then decide for each what they can view, create, edit and approve. Permissions are then applied consistently across the web and mobile interfaces and the API, and are checked during testing. Roles and permissions can be adjusted as the organisation changes.

Next step

Where does your team need access?

Tell us who needs access to your systems, on which devices, and what each role needs to see or update.