ERIKSLAIERsoftware workshop · Dnipro
Українська

Mon–Fri 09:00–18:00
Europe/Kyiv

Enquiry
Illustrative photo: a staircase and glass in a dark atrium with a copper band of light

ERIKSLAIER LLC · Dnipro

Software built like a building: with structure you can see

ERIKSLAIER is a workshop you bring a problem to, not a glossy deck. Mobile and web apps, UI/UX, publishing help and care after release. We talk straight, estimate in ranges and show results every week.

Bring a problem Rough out the scope

Work
mobile · web · UI/UX · publishing · care
Hours
Mon–Fri 09:00–18:00, Kyiv
Photo
illustrative, not our premises

Position

We’re a workshop, not an agency. No layers of management between you and the people writing the code, no forty-slide decks. A conversation, a teardown, an honest estimate and a result you can open.

People bring us new apps that must be ready by a specific date, inherited projects where nobody remembers how things fit together, and services that technically work but confuse people. The route differs for each, but the rules are the same: written scope, a range instead of one pretty number, and a visible result every week.

We don’t publish client logos, testimonials or awards — only what we can explain and back up in conversation. Photographs on this site are illustrative: they convey the mood of precise construction rather than showing our office.

The bench

Four jobs we do well

Not “full-cycle digital solutions”. Concrete jobs you can describe, estimate and verify.

Build

Mobile apps for iOS and Android and web apps that run in the browser. We write it so the next person can follow it without us.

Design

Flows, layouts, states and copy. Only what can really be built — errors, empty screens and long words included.

Launch

We prepare builds, copy and screenshots for the App Store and Google Play and run checks before a web release.

Care

After release — fixes, small changes, dependency updates. On working days, with clear priority rules.

Illustrative photo: a steel handrail with a copper tube

How a job moves

From talk to hand-over — six stops

No magic and no sprints for their own sake. Each step produces something you can see.

  1. Talk

    You describe the problem. We ask the awkward questions: for whom, why, what exists, what happens if nothing is done.

  2. Teardown

    We look at code, designs or alternatives. We write down risks and unknowns.

  3. Scope

    We fix what’s in, what’s out and under which assumptions. You get a range, not one pretty number.

  4. Build

    We work in short stretches. Each ends with something you can open and poke.

  5. Check

    We run the workshop standards: states, accessibility, screens, copy, rollback.

  6. Hand-over

    Code, access, notes. Then either care with us, or calmly without us.

Who walks in

Three situations at the door

Illustrative situations, not stories of specific clients. But if you recognise yourself, you’re in the right place.

“An idea and a deadline”

You know what you want, not how big it really is. We help cut the excess, ship a first working version and avoid burning budget on features nobody opens. We start with a short flow review and an estimate range.

“The developer left, the code stayed”

The app works, but nobody knows how. Updates are scary and the store keeps nudging about new requirements. We take the project apart, map the risks and hand control back: access, documentation, an update plan.

“It works, but people get lost”

Support complaints, abandoned forms, confusing buttons. We walk the product as a newcomer, note every point of friction and fix them in order — cheapest with the biggest payoff first.

Illustrative photo: a copper panel on a graphite stone wall

Mobile

In a pocket, on the move, on a weak signal

A mobile app lives in the worst conditions: shaky hands, sun on the screen, the metro with no signal. We design and build for that, not for a perfect simulator.

  • iOS / Androidnative or cross-platform, depending on the job
  • Offlineoffline states and request retries
  • Type sizelarge system font doesn’t break layouts

Web

In the browser, at any width

Dashboards, internal tools, sites with logic. Fast loading, keyboard use, forms that don’t lose input on error. Code the next team can read without a translator.

  • Phonechecked from 390 pixels
  • Tablet768 pixels
  • Monitor1440 pixels and wider

How we build

Launch

Pre-flight check

Publishing isn’t an “upload” button. It’s a list of things, each able to delay a release by days. Tick what you already have — a short version of our full tool.

0/5

Full check — 16 items

Care

We don’t vanish after release

Operating systems update, libraries age, users find paths nobody thought of. Care is an agreed number of monthly hours and transparent rules: what blocks work goes first; what gets in the way is scheduled; wishes are discussed.

There’s no 24/7 on-call. We say so up front so you can plan with open eyes.

Support form

Kyiv, now

Mon–Fri 09:00–18:00

MONTUEWEDTHUFRISATSUN

We don’t stand watch outside these hours. Messages that arrive in the evening or at weekends are picked up the next working morning.

Tools

Three tools to take with you

Free, no sign-up, everything runs in your browser. Switch tabs with the arrow keys.

Scope calculator

Tick features — sign-in, payments, maps, offline — and get a rough range in weeks with what inflates it. One click carries the result into an enquiry.

Open the tool

Standards

Eight rules before the word “done”

Standards in detail

States
Loading, empty, error, offline — all designed and built.
Keyboard
Every action works without a mouse; focus is visible.
Contrast
Text reads: 4.5:1 minimum for body copy.
Three widths
390, 768, 1440 pixels — no sideways scroll.
Words
A button says what it does. An error says what to do.
Rollback
Every release can be reverted.
Secrets
Keys and passwords don’t live in the code.
Note
Every change has a written note.

Straight talk

What we take on — and what we won’t promise

We take on

  • new apps from zero
  • inherited code after a teardown
  • redesigns of specific flows
  • publishing preparation
  • care on working days

We won’t promise

  • round-the-clock response
  • app store approval
  • top search spots or a million downloads
  • a fixed price without a scope
  • reviews and awards that don’t exist

Questions

The important bits, briefly

Didn’t find your question? Write to us — we reply during working hours.

Are you a studio or a freelancer?
We’re an independent workshop registered as ERIKSLAIER LLC. Small, with no sales department and no middlemen between you and the people writing the code.
Will you take on someone else’s code?
Yes. First a short teardown: we run it, read it and write down what we see. Then we tell you straight — fix, extend or rewrite a part. A full rewrite is the last option, not the first.
What does it cost?
It depends on scope. After a conversation you get a written description, assumptions and a range. Want a rough idea first? Try the scope calculator — it gives an indicative duration.
Do you guarantee App Store publication?
No, and nobody honest does. The store decides. We make sure everything on our side is prepared properly.
Do you work nights and weekends?
No. Mon–Fri, 09:00–18:00 Kyiv time. That keeps us attentive and estimates realistic.
What does a weekly result look like?
A link to a test version, a fresh app build or an updated layout — plus a short three-part note: what’s done, what’s next, what needs your decision. No long reports nobody reads, and no disappearing for a month.
What do you need from us at the start?
A few sentences about the problem, access to what already exists (code, designs, store account — via separate roles, not your password) and someone on your side who can make decisions. We’ll work out the rest together in the first conversation.
Who owns the code?
Code and access terms are written into the agreement before work begins. Our default: once paid, you get the code and all the access you need.
Illustrative photo: metal stairs in half-light

Got a problem keeping you up?

Describe it in a few sentences. We’ll read it, ask the awkward questions and tell you whether we can help — and how.

Send an enquiry devo@erikslaier.dev