Built for the hard parts

of mobile

Tablebase is a small, specialist consultancy.

You work directly with one senior mobile engineer rather than through account managers or a larger delivery team.

This works well when you need experienced engineering support for a specific mobile problem, project or gap in your team.

If you need a large team across several disciplines, a larger consultancy may be a better fit.

Start with a short call to discuss what you are building, the problem you are trying to solve and what you need help with.

You do not need to prepare a detailed brief beforehand.

If it looks like a good fit, I will send a short proposal covering the scope, engagement structure, availability and price.

The time between agreement and starting work depends mainly on availability, access and your onboarding process.

It depends on the type of work.

Scoped and advisory engagements can be relatively short if the problem is well defined.

Embedded engineering work usually needs enough time to understand the codebase, contribute properly and deliver useful results.

Start dates depend on current availability. I will give you a clear date before anything is agreed.

Yes. Most work is done remotely.

Working hours and overlap are agreed at the start of the engagement so there is enough shared time for meetings, pairing, reviews and technical decisions.

On-site work can also be arranged when it is useful, such as for project kickoffs, workshops or important delivery periods.

Usually, I work directly within your existing engineering environment.

That means using your repository, issue tracker, review process and communication tools, and working with your engineers where appropriate.

Some projects are better handled as a defined piece of work outside the day-to-day team. In those cases, the work is still delivered into your systems with documentation and a proper handover.

My main focus is native mobile development using Kotlin for Android and Swift for iOS.

I also work with Kotlin Multiplatform and can support existing Flutter or React Native applications.

The technology choice should depend on the product, existing codebase, team and technical requirements rather than a fixed preference for one approach.

Not necessarily.

In many cases, an existing application can be improved gradually without replacing everything.

This might involve separating problem areas, modernising parts of the architecture, updating dependencies or replacing individual modules while the product continues to ship.

Sometimes a rewrite is the right decision, but it should be based on the condition of the existing system, the cost of maintaining it and the risks involved.

The client owns the work produced during the engagement, including code, documentation, architecture and tooling, as agreed in the contract.

I am also happy to sign an NDA before discussing confidential technical details.

Client information, code and internal material are not used publicly without permission.

The goal is to leave your team in a position where they can continue without depending on Tablebase.

Code, technical decisions and important context are documented during the engagement rather than left until the end.

Before the engagement finishes, we will also agree on any necessary handover, transition period or follow-up support.

Tablebase is probably not the right fit if you need a large delivery team immediately or want one company to provide development, design, branding, marketing and other services together.

It is also unlikely to be the right fit if the main requirement is simply finding the lowest-cost development capacity.

The consultancy is best suited to situations where experienced mobile engineering support can make a meaningful difference to a project, product or engineering team.

If I do not think I am the right person for the work, I will tell you.

I work with technical recruiters and talent partners who need additional mobile engineering expertise for their clients.

That can include helping clarify a mobile engineering requirement, providing technical input during the hiring process or stepping in as temporary senior engineering capacity while a permanent hire is being made.

I can also take on short-term or specialist mobile work that may not make sense as a permanent role.

The commercial arrangement can be structured directly with the client or through the recruitment partner, depending on what works best for everyone involved.