RohallTechnologies Ltd · East Yorkshire
Exploded technical illustration of a software system drawn as stacked steel plates and bolts
Fig. 1 · Illustration generated for this site
Rohall Technologies · Market Weighton

Software, bolted together properly.

We design, build, publish and maintain web applications, mobile apps and websites. Each part is chosen for a reason, fixed in place with care, and written down so somebody else could take it apart.

  • AWeb applications for the work your team does every day.
  • BMobile apps for staff in yards, vans, warehouses and fields.
  • CIntegrations that join existing systems instead of replacing them.
  • DMaintenance so it still runs in five years.
R-01 · Plainly

What we are, without the varnish

Rohall Technologies Ltd is an IT company in East Yorkshire. We write software for organisations whose work is practical: manufacturers, agricultural and rural businesses, trades, logistics firms, charities and local services. Our clients' systems tend to run in sheds, workshops and vans as much as offices, and we build them to suit.

Our bias is towards robust over clever. We prefer established tools, readable code, documented decisions and modest hosting bills. When a spreadsheet or an off-the-shelf product would serve you better than a custom build, we will say so, even though it means less work for us.

We do not list clients, awards or headcounts on this site. Ask, and we will explain exactly who would work on your project and how.

R-02 · Bill of materials

What goes into a Rohall build

Part no.ComponentWhat it does for youSheet
R-010Web applicationBrowser softwareJob sheets, stock, bookings, inspections, records. Works on desktop, tablet and phone with one codebase.Apps & web
R-020Mobile appiOS and AndroidOffline-capable apps for people on the move: photos, signatures, barcodes and checklists that sync when signal returns.Mobile
R-030Interface designResearch and prototypesScreens shaped by watching the work, tested with real users before a line of code.Interfaces
R-040IntegrationJoining systemsConnecting accounting, stock, CRM or telematics systems through their published interfaces, with error handling that tells you when something fails.Integrations
R-050WebsitePublic faceFast, accessible websites with content you can edit yourself.Websites
R-060PublishingStores and hostingApp Store and Google Play releases, hosting, domains and certificates set up in your name.Publishing
R-070MaintenanceOngoing careUpdates, fixes, monitoring and a named route for support during working hours.Maintenance
R-03 · Assembly order

Five steps, fitted in sequence

Nothing is welded before it is measured. Every project follows the same order, scaled to its size.

  1. 1

    Survey

    We visit or video-call, watch the work and list every place information is written, copied or lost.

  2. 2

    Drawing

    A written scope and a clickable prototype. You approve both before building begins.

  3. 3

    Fabrication

    Built in two-week stages, each ending with something working that you can try.

  4. 4

    Fitting

    Data migrated, staff shown, published to stores or hosting under your accounts.

  5. 5

    Servicing

    Ongoing maintenance with updates, fixes and a clear support route.

R-04 · Try a tool

Draft your build sheet

Pick the parts and see the shape of a first release. It is a rough guide for a first conversation, not a price. Two more tools, an upkeep estimator and a launch check, live in the toolbox.

Screenprint-style illustration of a workbench with a laptop, circuit board, calipers and spanner
Fig. 2 · Generated illustration
Illustrative only, not a quotation

Build sheet

Tick the parts your first release needs. The sheet lists them like a bill of materials and shows a broad range.

Parts
TOTAL RANGE-
    R-05 · In the field

    Built for gloves, dust and no signal

    Offline first

    Works in a barn with no signal

    Field apps save every entry on the device immediately and synchronise when a connection returns. A clear counter shows what is still waiting to upload, so nobody wonders whether their inspection was saved.

    Big targets

    Thumb-sized controls

    Buttons and checkboxes sized for gloved hands and bright daylight.

    Evidence

    Photos and signatures

    Captured with time and location where you need proof of work.

    Scanning

    Barcodes and QR codes

    Use the phone camera to identify a pallet, part, machine or asset in one step, instead of typing a reference number on a small screen. Unknown codes are flagged, never guessed.

    Old kit

    Works on older phones

    We test on modest, older devices because that is what is often in the van.

    Exports

    Your data leaves easily

    CSV and PDF exports as standard. Lock-in is not a feature.

    R-06 · Interfaces

    Designed by watching the work

    A good interface comes from understanding the job, not from a style guide. We start by watching someone do the task as it is done now, with its shortcuts and workarounds. We then sketch the fewest screens that would make that task faster and test them as a clickable prototype with the people who will use them.

    We write labels in your words, keep forms short, and design error messages that say what to do next. Accessibility (contrast, keyboard use, screen readers, text size) is built in from the first sketch, not bolted on.

    Read the interface sheet

    R-07 · Publishing

    Released under your name

    Store accounts, hosting and domains are registered to your organisation. We are invited in as engineers. If we ever part ways, you keep everything without asking permission.

    App stores

    Listings, screenshots, privacy labels, testing tracks and review responses.

    Hosting

    Right-sized hosting with backups, certificates and a staging copy.

    Domains

    DNS and email records set correctly and documented.

    Handover

    A written operating guide for whoever looks after it next.

    R-08 · Tolerances

    The standards we hold ourselves to

    These are working standards, not marketing promises. Contract terms are agreed in writing per project.

    SpecToleranceHow you can check
    T-1Working build every two weeksA link you can open and use.
    T-2Accessibility target WCAG 2.2 AAChecklist issued with every release.
    T-3Code and accounts in your nameYou hold administrator access from day one.
    T-4Decisions written downA shared decision log you can read.
    T-5Backups restored, not just takenA test restore before launch.

    Full tolerances sheet

    R-09 · Maintenance

    Software needs servicing too

    Operating systems update every year. Browsers change monthly. Third-party services retire their old interfaces. Software that is not maintained does not stay still; it slowly stops working.

    Our maintenance agreements cover dependency updates, security patches, compatibility checks after major releases, bug fixes and help for your staff, Monday to Friday, 09:00 to 18:00. You report problems through a simple form and receive a reference for every request.

    R-10 · Questions

    Common questions at the bench

    Can you work with our existing system?

    Usually, if it has a documented way to exchange data. We check that early with a small test before committing.

    Do you only work in Yorkshire?

    No. Most work is done remotely across the UK. Site visits are arranged when they help and agreed in advance.

    Can we start small?

    Yes, and we usually recommend it. A first release that solves one problem well beats an ambitious one that arrives late.

    Who owns the code?

    You do, on payment, as set out in the written agreement. It lives in a repository under your account.

    R-11 · Next

    Send us the rough drawing

    A paragraph is enough: what job takes too long, who does it, and what happens to the information afterwards. We reply from systems@rohalltechnologies.bid during working hours, Monday to Friday, 09:00 to 18:00.