FAQ — Product

What is E-FACTS in one sentence?

Digital receipt infrastructure from POS → consumer wallet — returns, warranties, spend insight, and credible impact signals.

Where does the “real” product live?

The consumer iOS app is the daily product. Marketing tells the story; backend is the source of truth; docs align the company. See Surfaces.

What are the four tabs?

Home, My Bills, Analysis, Offers. Profile is a drawer, not a fifth tab. See Information architecture.

Why isn’t eco messaging louder?

Because we only surface impact when signals are real. Decorative greenwashing violates Principles.

How do we prioritize?

Job clarity → surface ownership → structured data → privacy → metric. Then apply P0–P4 bands. See Principles and Feature lifecycle.

Can we ship a feature only on the website first?

Only if the job is narrative / acquisition. Shopper jobs belong on iOS + API.

Where do design rules live?

Design language and canonical docs/Design.md. Product IA for tabs is documented there as reference — docs chrome uses a sidebar instead.

Who owns auth?

Backend issues and validates tokens; iOS stores them securely; docs site has a separate lightweight gate. Details: Auth & security.

What should I read before writing a PRD?

1. Users & personas
2. Principles
3. Surfaces
4. Feature lifecycle
5. Relevant Engineering page for the owning repo