Web & Mobile
Software meets people somewhere. That choice matters.
Web and mobile are not competing services — they are two places the same software can reach the person using it. The useful question is which surface the work actually happens in.
- Web applications, mobile applications, or both as one product
- Built for where the work happens, not where it is convenient to build
- Customer-facing and internal interfaces on one foundation
Two surfaces, one decision.
Web and mobile are not competing services. They are two places the same software can meet the person using it, and the useful question is which one the work actually happens in.
In a browser
Reach, and room to work.
- Suits
- Longer tasks, denser information, people at a desk
- Reaches
- Anyone with a link, nothing to install
- Trade-off
- Less present in the day — it has to be opened deliberately
On a phone
Close at hand, where the work is.
- Suits
- Short interactions, people moving, work away from a desk
- Reaches
- People who have installed it and kept it
- Trade-off
- Less room on screen, and more asked of the person first
Plenty of software needs both, with each surface doing the part it is suited to rather than the phone carrying a copy of the desktop screen.
What ITLC builds across both.
The same engineering foundation, delivered wherever the people using it are.
- 01
Web applications
Browser-delivered software where real work happens: records, submissions, review and the state of things.
- 02
Mobile applications
Software delivered on a phone, built for the shorter interactions that happen away from a desk.
- 03
Customer-facing interfaces
The surfaces people outside the organization use, where clarity matters more than density.
- 04
Internal interfaces
The surfaces staff use all day, where density and speed matter more than introduction.
- 05
Business websites
Sites that explain what an organization does and lead somewhere, built on the same foundation as the software around them.
Which technologies a build uses is decided during scoping. ITLC does not market a fixed stack, and no claim is made here about app stores, device support or offline behaviour.
A site that communicates, or software that works.
Both get called a website. They are not the same build, and knowing which one you need changes almost everything about it.
A site that communicates
Its job is to explain something and lead to a next step. Success is whether a visitor understood and acted.
Software that performs work
Its job is to let someone do something — record, submit, review, approve, track. Success is whether the work got done correctly.
ITLC's centre of gravity is the second. The first is built where it supports the software, not as a standalone offering.
When this is the work you need.
Usually it comes down to where the people using the software are standing.
The people using it are not at a desk
Work happens on a site, in a building, on a round — and getting back to a computer to record it means it gets recorded late, or not at all.
Something already runs the business
There is a system of record, and what is needed is a way for people to reach it that does not involve using it directly.
Customers need a way in
People outside the organization need to do something themselves rather than asking someone inside it to do it for them.
What you are left with.
Software people actually open
Built for where the work happens rather than where it would be convenient to build for.
One foundation, not two codebases of habit
Web and mobile treated as surfaces of the same product rather than unrelated projects.
Interfaces that survive change
Adding a screen does not mean reconsidering how every other screen was put together.
Recorded at the point it happens
Work captured where it occurs instead of remembered and entered later.
Start from where the work happens.
Who uses this, and where are they standing when they do? That answer usually settles the surface question before anyone discusses technology.