Service
Custom software and applications
Managing cases, recording field observations or offering a customer service requires workflows and functions suited to the activity. The service covers defining those uses, designing interfaces and developing the software, including its data, integrations and operating requirements. Work can cover a new application or changes to an existing tool.
Software shaped around the work to be done
Build a shared working process
Handling a request or case involves information, statuses and responsibilities. Design work establishes the screens, rules and permissions required at each step. The software makes it possible to review progress, trace decisions and pass information to the people involved.
Connect an application to existing systems
A new function may need customer records from a CRM, orders from an ERP or documents stored elsewhere. API and integration development establishes where data is managed and how changes are passed between systems. Updates and exchange errors can then be tracked across applications.
Extend an existing tool and its uses
Adding mobile access, a customer workspace or a calculation rule requires examining the code and data already in use. Work is divided into verifiable functions, with business-rule tests and migration of the relevant data. Release planning covers the transition to the new version and follow-up with users.
The proposed engagement
The engagement can cover scoping, architecture and application development, or a defined part of an existing project. Workflows are reviewed through mockups and working scenarios. Development brings together interfaces, business rules, data and APIs, with testing and deployment preparation.
An example scope
For field-service tracking, a scope could combine a data-entry application, photographs and an office workspace for reviewing records. Offline access, synchronisation and report generation would be defined with users before development.
An agreed scopeThe scope defines the functions to deliver, the data to migrate, the systems to connect and the conditions for release.
What the delivery includes
- Agreed workflows and mockups, documented business rules and acceptance criteria for the selected functions.
- Version-controlled source code, user interfaces, application services and a data model.
- APIs and exchanges with the relevant systems, with business-rule and integration tests.
- Deployment procedures, data migration within scope, documentation and agreed maintenance arrangements.
Integration with your environment
- Web, mobile or desktop delivery depends on users, devices and any need for offline access.
- Existing business software, databases and identity services are accounted for in the design.
- Hosting, application distribution and maintenance are agreed with the people who will operate the software.
Service lineApplications and integration →
Plan the first stage
The first discussion describes a concrete workflow, its users, the information involved and the systems to connect. A workshop or review of the existing application can produce mockups, a prioritised scope and an estimate for the first delivery. Acceptance criteria are agreed before development so the result can be checked against representative working situations.
Related projects
The related projects describe contributions to APIs, scientific software and application tools. Limen also illustrates a mobile workflow, data capture and document generation. Each reference identifies the functions built and their context.
The Limen application
Limen prepares property inspection records, captures observations and photographs, collects signatures and generates a PDF report. It runs locally on the phone, illustrating on-device storage, mobile workflows and document generation. It is currently in closed testing.
Explore the app and its PDF output →Services by sector
Explore the engineering services offered across different sectors.
Banking and insurance
Banking APIs and data applications
Development of services accessing accounts, transactions and positions through available interfaces and granted permissions. Portals and analytical applications preserve processing statuses and transaction references.
Energy and utilities
Applications and operational interfaces
Web applications, portals and dashboards for series, assets and calculation results. Integration of alerts and business data with filters by site, period and source.
Logistics and supply chain
Web and mobile applications
Interfaces for viewing, scanning and collecting documents for authorised operations. Local storage, synchronisation and access permissions for shipments and documents.
Manufacturing
Monitoring and quality applications
Web or mobile interfaces for viewing measurements, recording inspections and linking observations with production references. Permissions, attachments and synchronisation with connected systems.
Retail and e-commerce
Web services and mobile applications
Development of storefronts, customer portals and business tools connected to accounts, products and orders. Search, viewing and tracking interfaces with access permissions and data synchronisation.
To go deeper
A mobile application stays consistent through its synchronisation protocol
Operation identifiers, retries and concurrent-update handling between a mobile application’s local database and its server.
Defining the exchange contract between APIs and events
Transactional publishing, retries and message-schema evolution between an order application and its read projections.
Reliable reporting without replacing every tool
Defined metrics, identifiable sources and a tested first pipeline provide a foundation that teams can explain and extend.
Related solutions
Discuss your project
A discussion of your project’s design, development and production deployment.