The approach
How we work on it
- Decide whether a native Android app, a progressive web app or a responsive site fits the need.
- Design for small screens, poor connectivity and one-handed use.
- Build against a secured API, with tokens and role checks on the server.
- Test on real devices before each release.
What you receive
Typical deliverables
- Recommendation on app type
- Working app or mobile-first web application
- Secured API where needed
- Release and update plan
What we will and will not promise
Our documented mobile delivery is Android (Kotlin) and mobile-first web. We say plainly when a requirement, such as native iOS, is outside what we currently deliver.
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.