> For the complete documentation index, see [llms.txt](https://docs.bitpers.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitpers.com/introduction/why-and-how.md).

# Why & How

### The Problems (Today’s Reality)

* **Scattered sharing:** Photos split across chats, drives, and feeds.
* **Lost discoverability:** Hard to find your own or others’ photos from shared events.
* **Zero collaboration:** No structured way to decide, edit, or curate together.
* **Shallow engagement:** Brands and creators rely on ads, not authentic communities.

### The Solution (Bitpers)

#### Modular System

* **Murals:** Dynamic, customizable boards (private → public).
* **Memory Boards:** Auto‑filled diaries and group storybooks.
* **Collab:** Decision layer—polls, ranking, tags, quick edits.
* **Events:** Time‑bound context; routes media to the right spaces.
* **Face Hunt:** Consent‑first people search (opt‑in); fast recall.

#### Principles

* **Privacy & consent:** Opt‑in discoverability; friend‑based visibility.
* **Performance:** Prefetching, optimistic UI; local‑first approach.
* **Clarity:** Media stays front‑and‑center; minimal chrome.

### Why Now (Signals & Numbers)

* **UGC explosion:** \~**1.7T photos/year** created globally; most remain unused.
* **Cultural shift:** Gen‑Z/Alpha favor **niche communities, privacy, and creation tools** over performative feeds.
* **Category proof:** Reddit & Pinterest show sustained growth for **interest‑based, visual discovery**.
* **Tech readiness:** On‑device AI + modern privacy frameworks enable **face/people features without central harvesting**.

### Market Opportunity

| Tier    | Description                           | Size          |
| ------- | ------------------------------------- | ------------- |
| **TAM** | Global visual & UGC collaboration     | **$50B+**     |
| **SAM** | Event, creator, and SMB visual tools  | **$8B**       |
| **SOM** | Weddings, colleges, micro‑communities | **$200–300M** |

**Initial GTM:** Indian weddings, colleges, bike clubs, creator collectives → expand to global communities.

### How We Win (Execution)

* **Go‑to‑market loops:**
  * *Weddings & Studios:* Event Murals + Collab sorting → guests join → recurring boards.
  * *Campuses & Clubs:* Private murals for fests/projects → topic hubs.
  * *Creators & Brands:* Collab for campaign curation → public murals with authentic engagement.
* **Product flywheel:** Events route media → Memory Boards & Murals → Collab decisions → shareable outcomes → discovery.
* **Trust moat:** Consent‑first Face Hunt; transparent visibility; encryption roadmap.

### Roadmap (Illustrative)

1. **Prototype (now):** Android MVP with Murals/Boards; partial Collab.
2. **Build & Test (≤6 mo):** Scalable backend + encryption; internal events.
3. **Controlled Rollout (≤12 mo):** Android + iOS; weddings/colleges/creator pilots.
4. **Cross‑Platform (≤18 mo):** Desktop + web; brand & influencer onboarding.
5. **Scale & Monetize (≤24 mo):** Paid creator tools; 100k+ users; brand collaborations.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bitpers.com/introduction/why-and-how.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.