ПЕРЦЕПТРОНdecision engineering
/SERVICES4 AREAS

Four areas. One way of thinking.

For each area — what is included, which questions we ask first, and by what signs the work counts as finished. Cost and timescales are set after the task is clarified.

Mobile development · App UI/UX design · Websites · Release assistance

Mobile development

MOB / AREA

An app makes sense when people come back to it regularly. We start by asking whether an app is really needed or a responsive site would do.

Included

  • Scenario map and first-version priorities
  • Choice of approach: native or cross-platform — with the trade-offs explained
  • Development, test builds, fixes
  • Preparation for store submission

Starting questions

  • Who are the main users and on which devices?
  • Are sign-in, payments or offline mode needed?
  • Who will own the Apple and Google accounts?

“Done” criteria

  • The build runs on agreed devices
  • Core scenarios pass a written checklist
  • Known limitations are listed

App UI/UX design

UX / AREA

Design is a way to make decisions visible before they become expensive in code. We show structure and flows before colour.

Included

  • Screen and navigation structure
  • Interactive prototype of key flows
  • Interface with states: empty, loading, error
  • Hand-off specification for development

Starting questions

  • What should a person achieve in the first two minutes?
  • Which data may be missing or wrong?
  • Is there an existing brand style to keep?

“Done” criteria

  • Text contrast is checked
  • Touch targets meet the agreed size
  • Every screen has a described error state

Websites

WEB / AREA

A company website is often the first thing people see. It must work on a modest phone, read without effort and honestly report what happened to a form.

Included

  • Page structure and copy developed with you
  • Responsive layout at 390 / 768 / 1440 px
  • Forms with server-side validation and honest messages
  • Several language versions if needed

Starting questions

  • Who hosts the site and is there a mailbox on the domain?
  • Who will write and update the copy?
  • What data do the forms collect?

“Done” criteria

  • No horizontal scrolling at 390 px
  • Navigation works with a keyboard
  • Privacy notice matches the real forms

Release assistance

REL / AREA

Finished code is not yet a published app. Release requires materials, accounts and checks that are often remembered on the last day.

Included

  • Audit of build readiness for submission
  • Listing copy, screenshots, categories
  • Data-safety forms and privacy policy
  • Support during store review

Starting questions

  • Are developer accounts created in the owner's name?
  • Who will respond to reviewer comments?
  • Is there a support page and contact email?

“Done” criteria

  • All mandatory store fields are complete
  • Data form matches the app's real behaviour
  • There is a plan if the submission is rejected

Combinations

Areas can be combined: for example, UI/UX design and a website for one launch, or release assistance alone for an app built by another team. In that case we first check the build and access, and only then agree timescales.

Separate IT support for products already launched is available — see the support page.

Assess brief readinessDiscuss