Web applications for your business

Web apps for shared workflows

A web app opens in a browser and helps people complete a task. For example, they can record cases, add information and produce a report. Kotodama develops applications like these for businesses and organisations with a clearly describable process.

Discuss a browser application
Work together in the browserEvery task
has its place.
Inbox 01
DEVICE 12Check returnPhoto missingTeam A
In progress 01
TASK 08Handover
report
✓ Details○ ReviewTeam B
Ready 01
DEVICE 04Maintenance loggedNote added
An example workflow view with fictional entries.

A process has a beginning and a result

Equipment management is one example: an employee records an item, another person reserves it and its condition is added when it returns. Each step needs the right information and a responsible person.

Other web applications can process orders, manage registrations or make a specialist directory searchable. A mobile guest guide is another possibility for hotels. If your main concern is scheduling and resource conflicts, see planning tools.

Shared data needs clear rules

We define which records belong together and who edits them. This includes required information, search and filter options, and changes after approval. When people work simultaneously, the application must handle conflicting inputs.

Existing lists can be imported after review. For interfaces, we clarify field mapping, error handling and responsibility for incorrect source data. An export can be part of the handover so agreed information remains usable elsewhere.

A web app, standard software or a mobile app?

If an existing solution covers your workflow, configuration may be enough. A custom web app becomes useful when business rules or the relationship between steps need a tailored implementation.

Browser use can also be designed for phones. Special device features, offline work and distribution as an installed app are assessed separately. Mobile app development covers these decisions. For external users working with documents and approvals, see customer portals.

Before launch: access, operation and cost

You show us a complete example case and involve the people responsible for the main business rules. The quote describes features, roles and supported devices. Data migration, file uploads and connections to other systems influence the work involved.

Hosting, backup and recovery are agreed before rollout. For sensitive information, we clarify the actual requirements early. During acceptance, we run normal and error cases, test access with different accounts and agree on instructions for your users.

Common questions before starting

Does every user need to install something?

A standard web app is accessed through an address in a supported browser. Login and any additional device requirements depend on the project.

Does it work without internet?

This needs explicit planning. We determine which information is available locally, which changes remain possible and how later synchronisation works.

Can the application grow later?

Further features can be commissioned. We identify foreseeable extensions when defining the first scope, without claiming they are already included or unlimited.

Rafael HagerYour contact
Rafael Hager

The first step

Which process should work in the browser?

Who handles the process, and when is it complete for you?

All software services ↗