Engineering, maintenance and testing
Fast, secure software.
One partner for all of it.
I engineer web and mobile solutions, keep them running and prove they work. Development, maintenance and testing in one place, with no handovers.
Illustrative interface with demo data.
Everything in one place.
Engineering, maintenance and testing from one engineer. Hire one part, or let me own the whole lifecycle.
Engineering and development
Fast, secure solutions built to be run and extended.
- Web apps and admin panels
- Android and iOS apps with Flutter
- APIs, databases and integrations
- Secure by design: roles, auth, safe defaults
Maintenance and support
Keep it running, safe and up to date.
- Bug fixing and small features
- Updates and security patches
- Monitoring and backups
- Priority support when it matters
Testing and QA
Catch problems before your users do.
- UI, API and regression automation
- Exploratory and mobile device testing
- QA audits and test strategy
- Release readiness checks
Security and delivery
A pipeline that keeps releases safe.
- CI/CD pipelines
- Quality gates on every merge
- Dependency and access checks
- Test environments and reports
Built for the job site. Tested like it matters. A construction platform for crews on the move, from the first tap to the last report.
Made for the people on the ladder.
One app for the whole crew: clock in on site, log materials, check out machines and see approved hours. Short flows, big buttons, no training needed.
Today
Within site radius
Hours
Stock
Machines
Shift logged
Log material
Excavator E-14
Illustrative app with fictional names and demo data.
Every site in one view.
Projects, crews, materials, machines and vehicles, with reports that answer what is happening today.
Hours captured on site.
Clock in from the phone, approve in seconds, export for payroll.
Made for gloves and sunlight.
One Flutter codebase for both phones. Big buttons and short flows for the few actions workers need on site.
Simple to run.
A lean stack that fits the project: web admin, API and a database chosen for the job, served over HTTPS.
iOS
Web admin
Secure
roles and auth
right fit
Everyone sees what they should.
Separate roles for super admin, admin, client portal and workers. Access rules are treated as features and covered by automated tests, so a change cannot quietly open a door.
Illustrative interface with demo data.
Release with confidence.
UI, API and regression suites run on every change, so a broken login, a lost timesheet or a failing integration shows up in minutes, not in production.
Requirements become real user journeys with clear acceptance criteria.
Every criterion becomes a test case.
- ●Zero-hour week approves without errors
- ●24 h in one day is rejected with a clear message
- ⚑Overtime total changes after approval. Needs a bug report.
Approving a timesheet resets the overtime total
- Open a week with 41.5 h logged
- Click Approve
- Look at the week total
Cause found: the total is capped at 40 h when a week is approved.
Under the hood
Real user journeys, automated.
Browser automation walks the app like a worker or a manager would and checks the result in the UI and through the API.
- Page objects, so tests survive UI changes
- Selectors by role and label, not fragile paths
- Screenshot, video and trace on every failure
- Tests run in parallel across browsers
- ✓ worker clocks in on site1.2s
- ✓ manager approves timesheet1.8s
- ✓ admin creates a project2.1s
- ✓ material is logged from phone1.4s
- ✓ client sees only own sites0.9s
- ✓ export hours for payroll2.6s
- 6 passed (chromium, firefox, webkit)
See what changed, on every screen.
Every build is compared with an approved baseline, so a button that moved or text that overflows is caught before a customer sees it. Drag the handle.
- Visual comparison against approved screens
- Responsive checks from phone to desktop
- Android and iOS device runs
- Accessibility checks in the same run
Sample layout of a visual comparison.
Releases do not break what worked.
A regression suite re-checks the core flows on every release, across web, Android and iOS.
- Critical flows first, full suite every night
- Flaky tests tracked and fixed, not ignored
- Every escaped bug becomes a permanent test
- Coverage map by module and platform
Approving a timesheet resets the overtime total
Sample finding and coverage layout.
Services agree before users find out.
API and integration tests check that the apps, the server and external systems agree on data, roles and errors.
- Contract tests between apps and API
- Role and permission checks on every endpoint
- Test data created and cleaned up by the tests
- External integrations stubbed and verified
test('worker cannot approve hours', async ({ request }) => { const res = await request.post('/api/hours/42/approve', { headers: workerAuth, }); expect(res.status()).toBe(403); }); test('timesheet matches the contract', async ({ request }) => { const res = await request.get('/api/hours/week'); expect(await res.json()).toMatchSchema(timesheetSchema); });
A quality gate on every merge.
Tests run automatically in your CI/CD pipeline. Code that fails the gate does not reach production.
- Runs on every pull request and every night
- Parallel shards keep feedback fast
- Merge blocked until the checks pass
- Reports published with every run
name: quality-gate on: [pull_request] jobs: e2e: runs-on: ubuntu-latest strategy: matrix: shard: [1, 2, 3] steps: - uses: actions/checkout@v4 - run: npm ci - run: npx playwright install --with-deps - run: npx playwright test --shard=${{ matrix.shard }}/3
Example workflow and pipeline layout.
The more hours, the lower the rate.
Choose what you need, then drag to size your monthly retainer. The rate steps down as the hours go up, and you get a clear quote after a short call.
Rates are agreed per project after a short call. Fixed-scope projects, MVPs and audits are quoted individually.
Let's talk about your next project.
Tell me what you want to build, keep running or test. You get a short plan and a quote that fits the scope.