EMRE

Home / Standards

Delivery standards

The rules on the inside of the lid

Written standards, so you know what to expect and can hold us to it.

Visibility

  • A working build every second week, installable or viewable on your own device.
  • A shared document listing what is in progress, what is next and what has been parked.
  • Problems reported when we find them, not at the end of the slice.

Code

  • Version control in a repository you own from day one.
  • Peer-reviewed changes and automated tests for data handling.
  • Dependencies kept current and listed with their licences.
  • A README that lets a new developer run the project in an afternoon.

Security and privacy

  • Collect the least data the product needs.
  • Secrets kept out of source code.
  • Access granted per person and removed when work ends.
  • Privacy notice and store declarations checked against the real behaviour.

Accessibility

Designed and tested towards WCAG 2.2 AA: contrast, keyboard and screen reader use, text scaling, reduced motion. Known gaps are listed with a plan, never hidden.

Change

Changing your mind is normal. When a new idea arrives mid-build we say what it would displace, how it affects the next demo and whether it belongs in a later slice. You decide.

What we do not claim

We do not quote fixed timelines before the riskiest question is answered, we do not promise store approval, and we do not provide regulated financial, legal or medical advice inside the products we build. Where a product touches those areas, we expect you to involve the appropriate qualified professional.