1. Home
  2. Services
  3. Mobile apps

APPS FOR TEAMS AND CUSTOMERS

Mobile apps for iOS and Android

Your colleagues search for documents on their phones or wait until they are back at a computer to finish a task. We build mobile apps around their work, with access to the information and features they need.

MedProtocol, a web platform and mobile apps built by Webmate
FROM THE MEDPROTOCOL PROJECTWeb, iOS and Android

COMPANIES WE HAVE BUILT FOR

Orange
TTC
APCI
Meliora
Maison D'Esthetique
London Brothers
Fan Telecom Technology
iFactory3D
Center Electric
DeCasă
MedProtocol

SOUND FAMILIAR?

What should your team be able to do from a phone?

01

Colleagues hunt for the latest document.

The team compares files and messages before they know which version they can use.

02

The same task is redone at a computer.

A colleague makes notes on a phone, then copies them into a program and checks the details again.

03

Every role sees the same screens.

Users scroll through information that does not concern them before they find their task.

IN SHORT

What Webmate builds for the phone.

The Webmate team builds mobile apps for iOS and Android, together with the web administration and the integrations they need. We start from user tasks and agree what information each user can view or change.

For MedProtocol we built a web and mobile platform for protocols, training and notifications. Staff see the resources that match their role, and managers can follow training progress.

  • Account and resource access by role.
  • Documents and information managed through the web platform.
  • Notifications and actions defined for each user.
  • Integrations with your existing software, after we check access.

CHOOSING THE PROJECT

An app starts with the task the user repeats.

We check whether a mobile-friendly website meets the need or whether you need an installed app. The choice depends on how often people use it, access to device features and working conditions.

The budget depends on features, roles, integrations and the platforms we launch on. Offline use, data stored on the phone and sync are agreed separately, when you need them.

Apps usually connect to a web platform or to your business systems. See how we approach business systems and API integrations between business systems.

  • User tasks and the screens they need.
  • The data each role can view or change.
  • The link with your web platform, ERP or CRM.
  • The devices we test the app on.
  • Publishing accounts and responsibility for updates.

WHO WE BUILD FOR

An app for your team or an app for your customers.

The two types of app start from different questions and are published differently.

Mobile apps for teams and for customers
CriterionApp for your teamApp for your customers
Who uses itColleagues: medical staff, technicians, sales agents, warehouseYour customers, on their own phones
What they do in itCheck procedures, fill in forms, receive tasksOrder, book, see their account and history
What matters mostRole-based access and the link with internal systemsSimple screens and a reason to install it
How it reaches the phoneFrom the App Store and Google Play, with access only for company accountsPublicly, from the App Store and Google Play
ExampleMedProtocol: protocols and training for hospital staffAgreed around your sales model

WHICH TYPE OF APP

Native app, cross-platform app or mobile-friendly website.

The choice changes the cost, the device features the app can use and the way you update it.

The technical options for a mobile app
CriterionNative (Swift and Kotlin)One codebase for iOS and AndroidMobile-friendly website
CodeSeparate for iOS and AndroidOne codebase, published on bothOne website
Camera, notifications, offline useFull accessAccess to most featuresLimited access
PublishingApp Store and Google PlayApp Store and Google PlayNo app stores
Effect on budgetLarge, two appsMediumSmall
Best forDaily use and phone featuresCommon features on both platformsOccasional use, no install

The MedProtocol apps are native: Swift for iOS and Kotlin for Android, connected to the same web platform.

WHAT MOVES THE PRICE

The factors that change an app budget the most.

The effect comes from the proposals we write. It compares factors and is not a rate card.

What moves the budget of a mobile app
CriterionEffect on budgetWhy
Both iOS and AndroidLarge for native appsTwo apps, built and tested separately
Different rolesMediumEach role sees different screens and data
Offline useLargeData is stored on the phone and synced when the connection returns
Link with your ERP or CRMLargeAccess, permissions and error handling are built for each program
Web admin platformMediumSomeone has to add content and users without a developer
NotificationsSmall to mediumRules for who receives what and when

PUBLISHING

What publishing on the App Store and Google Play costs.

App store fees are public and are paid directly to Apple and Google from your company account.

Developer accounts for publishing apps
CriterionPublic feeIn whose name
Apple Developer Program99 USD a yearYour company, so the app stays yours
Google Play Console25 USD, one-time feeYour company, so the app stays yours

Apple and Google review every app before it goes live. We plan the launch with that review in mind.

FROM OUR WORK

An example from our work

MedProtocol: protocols and training on web, iOS and Android.

Protocols and documents were split across folders and files that were hard to update. We built the web platform and mobile apps with role-based access, search, training and notifications. Staff can check the same up-to-date version of the resources on the device they use.

See the MedProtocol project
Web + iOS + AndroidPlatforms
Protocols and trainingUse
The MedProtocol platform for protocols and staff training

HOW WE WORK

How we prepare the app for daily use.

01

We follow the user’s tasks.

We clarify what they do on the phone, what data they need and what stops them from finishing today.

02

We build and test with your team.

We test screens, role-based access and integrations on examples from your daily work.

03

We prepare launch and support.

We agree publishing, accounts, updates and how users report problems.

FREQUENTLY ASKED QUESTIONS

What you may want to know
before we start.

Platforms, data access and support are agreed in the proposal.

Do you build apps for iOS and Android?

Yes. MedProtocol is a Webmate project with a web platform and apps for iOS and Android. For each project we agree the devices, features and administration before development.

Do we need a mobile app or a website that works well on phones?

We start from what the user needs to do and how often. If a mobile-friendly website covers the need, we keep it as the option. An app is justified by specific tasks and features.

Can the app use data from our ERP or CRM?

We check the available access, documentation and permissions of your current system. After that check we confirm what a user can view or change from the app.

How much does a mobile app cost?

The cost depends on features, user roles, the platforms you choose and integrations. The proposal separates development, store submission and maintenance, including any third-party platform fees.

Can the app work without internet?

We discuss which information must be viewed or filled in offline and what can be stored on the device. Sync rules and the limits of offline use are agreed separately in the project.

What does publishing on the App Store and Google Play cost?

Apple charges 99 USD a year for the Apple Developer Program, and Google charges a one-time 25 USD fee for Google Play Console. The accounts are opened in your company’s name.

Do you build native apps?

Yes. The MedProtocol apps are native, written in Swift for iOS and Kotlin for Android. For other projects we choose the technology based on features and budget.

Who handles publishing and updates?

The proposal states who owns the accounts, who prepares each release and who maintains the app. Publishing also depends on Apple and Google reviews, and later updates need a named owner.

NEXT STEP

What should your team be able to finish from a phone?

Describe one task and who does it today. On the first call we clarify what the app should include and which systems we need to check.

Book a call

HOW THE STEPS CONNECT

  1. Sales

    The team records the order.

  2. ERP and stock

    Checks the products and documents.

  3. Warehouse

    Prepares the order.