ЮНІТІprogramming

FIELD NOTES

Resources for people assembling a product

Short working notes, no filler. Use them even if you never work with us.

N-01

How to cut a mobile app MVP

  1. Write down the one action a person opens the app for. Anything not leading to it is a "later" candidate.
  2. Instead of full registration first, use guest mode or email magic-link sign-in.
  3. Admin features can often be covered temporarily by a simple web panel.
  4. Postpone everything "social" (comments, follows) until you have a core user base.

N-02

Native or cross-platform: an honest comparison

  1. Cross-platform (React Native, Flutter) pays off when UI is the same on both platforms and logic outweighs hardware.
  2. Native is justified for heavy camera, BLE, AR or background processing.
  3. A hybrid is possible: shared core plus native modules for bottlenecks.
  4. The key question is who maintains the code in a year and which team you can hire.

N-03

Pre-submission checklist for App Store and Google Play

  1. Developer accounts under your company, D-U-N-S number obtained early (for Apple).
  2. A reviewer test account with full feature access.
  3. A privacy policy at a public URL matching the privacy questionnaire.
  4. In-app account deletion if registration exists.
  5. Screenshots for all required screen sizes.

N-04

How to write a brief that can be estimated

  1. Who the users are and how many types (customer, provider, admin).
  2. The three most important end-to-end journeys.
  3. What already exists: design, backend, payment provider agreements.
  4. Constraints: date, budget corridor, regulatory requirements.

N-05

Mobile app accessibility: the minimum

  1. Labels for VoiceOver and TalkBack on every icon button.
  2. Support system font size without truncation.
  3. Text contrast of at least 4.5:1.
  4. Never convey information by colour alone.

N-06

What you should own after a project

  1. Admin access to the code repository.
  2. Store, cloud, domain and email accounts under your company.
  3. Architecture document and deployment runbook.
  4. A list of third-party services with terms and renewal dates.