MiksoraIT partner · Dnipro

Home / Guide

Guide

Before the first conversation

A few materials to help you prepare — even if you end up choosing another team.

Illustrative mood photo: A few notes before the first conversation.
A few notes before the first conversation.

What to gather in advance

  • one or two sentences: who the product is for and what it does
  • links to a live version or layouts, if any
  • the three things that bother you most
  • user feedback or requests (without personal data)
  • preferred timing and constraints

Questions to ask any team

  • Who exactly will work on the product?
  • How do you report problems and delays?
  • What happens to the code and access afterwards?
  • What isn’t included in the estimate?
  • How is accessibility checked?
Illustrative mood photo

A good estimate has three parts: what’s done, under which assumptions, and what is consciously left out.

MIKSORA

A short glossary

Release
A product version made available to people.
Interface state
How a screen looks in a given situation: loading, empty, error, success.
Accessibility
The ability for people with different needs to use the product: by keyboard, screen reader, large font.
Dependency
A third-party library the code relies on. It needs periodic updates.
Regression
When a change accidentally breaks something that used to work.
Layout / mockup
A picture of a screen before it’s built. Useful when it reflects real data and states.

How to read a work estimate

A good estimate has three parts: what’s being done, under which assumptions, and what is consciously left out. If an estimate lists no assumptions, it’s probably imprecise.

Look for ranges: “three to five weeks” is more honest than “exactly four weeks”, because there is always more unknown at the start.

How much does an app cost?
There’s no single answer: it depends on screens, integrations, platforms and support needs. We estimate after a conversation and scope description.
Do I need an app if I have a site?
Not always. Sometimes improving the mobile site is enough. We’ll say honestly if an app doesn’t seem justified.
What is hour-based support?
An agreement for a set number of monthly hours for requests and improvements. We don’t silently burn unused hours — we discuss how to use them.