The approach
How we work on it
- Confirm which features need installability, offline use or notifications.
- Build one responsive codebase served over HTTPS.
- Add a web app manifest and a carefully scoped service worker for caching.
- Test on the browsers and devices your users actually have.
What you receive
Typical deliverables
- Installable web application
- Caching and offline behaviour agreed per screen
- Browser and device test notes
- Update and cache-clearing plan
What we will and will not promise
Browser support for some features differs by device. We list what works where rather than promising identical behaviour everywhere.
How an engagement runs
Discover, propose, deliver, support
The same four stages apply to every Incipit practice, so you always know what has been agreed and what happens next.
- 01
Discover
We learn the business need, the people who will use the result and the constraints, before any solution is proposed.
- 02
Propose
Scope, milestones, responsibilities and ownership are agreed in a written proposal.
- 03
Deliver
Work is built in milestones. You review working builds and approve each stage before the next begins.
- 04
Support
Handover of code and documentation as agreed, with maintenance and support available afterwards.
Technology
What we build with
- ASP.NET MVC
- C#
- Entity Framework
- SQL Server
- Microsoft Azure
- Android (Kotlin)
- Bootstrap
Questions
Before you enquire
Related work
Where Incipit has done this
Related services
Describe what you need
Tell us the requirement and your time zone. We reply with questions, options and a written proposal.