The Solutions Jar

The Solutions Jar is a self-reported mobile-first web application designed to support emotionally healthy communication in intimate relationships. The author describes it as a digital version of a physical ritual where individuals write down difficult feelings, place them in a shared "jar," and return to discuss them later. It is positioned as a tool for managing conflict through structured emotional expression and reflection.

The product is built using vanilla JavaScript, HTML/CSS, and serverless technologies (Cloudflare Workers, D1), with an emphasis on privacy via private links and a 21-day lifecycle for content.

The description states that The Solutions Jar is a private, mobile-first communication app. It allows people to express difficult feelings by writing them down in a digital notebook, choosing whether to save as draft or place into a shared "jar." Jars represent relationships or personal reflections and are accessed via private links.

Key features include:

• A visual jar that changes based on how many papers (feelings) are inside.
• Papers can be addressed intentionally, not automatically pulled from the jar.
• Drafts and completed papers are removed after 21 days.
• The app is built as a Progressive Web App (PWA), allowing offline access and home-screen installation.

It is described as not a messaging app, task manager, or dashboard — but rather a ritual-based tool for emotional processing.

Claim: The product turns the physical act of writing feelings into a digital experience.

Evidence: Author’s own write-up; technology stack includes HTML/CSS/JS, Cloudflare Workers/D1, PWA components.

The author positions The Solutions Jar as a way to preserve emotional connection during conflict by using a structured, non-immediate form of communication. It is framed as an alternative to arguing in the moment or avoiding difficult conversations altogether.

It evolved from a personal solution used by the founder and her partner after experiencing family abuse and unhealthy dialogue. The app was inspired by their physical jar ritual and aims to bring that same sense of safety and intentionality into digital interaction.

Claim: It helps people communicate healthily, especially when emotions are high.

Evidence: Author's narrative; the inspiration section describes how it helped them avoid re-litigation of past issues.

Claim: The app preserves relationships while addressing root causes.

Evidence: Author’s own write-up; emphasis on reading aloud, thoughtful response, and intentional discussion.

The description does not clearly define a specific customer segment or ideal customer profile (ICP). However, it implies the target is individuals in intimate relationships who struggle with conflict resolution and emotional expression.

It is designed for people who:

• Value emotional safety in communication.
• Want to avoid shutting down during difficult conversations.
• Prefer taking space before discussing issues rather than immediate confrontation.

Claim: The app targets couples or close relationships where communication styles differ.

Evidence: Author’s personal experience; the physical jar was used between partners with different communication tendencies.

Claim: It supports people who want to express themselves without pressure.

Evidence: Drafts can be edited until ready to share; no obligation to post immediately.

There is no evidence of a business model or pricing structure in the description. The author does not mention monetization, subscriptions, or any form of paid service.

Claim: No revenue or pricing data provided.

Evidence: Entirely self-reported; no mention of charges, plans, or monetization strategies.

The app is built using:

• Vanilla JavaScript
• HTML/CSS
• REST API and serverless infrastructure (Cloudflare Workers/D1)
• PWA features including manifest, service workers, caching
• GPT-5.6 and Codex for development assistance

It uses a visual metaphor of a glass jar that updates dynamically with paper count. The UI includes animations to simulate placing papers into the jar.

Claim: It is a lightweight, mobile-first web app.

Evidence: Author’s own write-up; mentions PWA structure and responsive design.

Claim: Data is stored in Cloudflare D1 (SQL database).

Evidence: Technology tags and developer notes.

There is no evidence of traction, users, or adoption beyond the author's own development efforts. The project is described as an MVP built by a single person.

Claim: No data on usage, retention, or user engagement.

Evidence: Self-reported only; no metrics, customer list, or performance indicators.

The description does not reference competitors or similar products. It does not describe how the app compares to existing tools for emotional communication or relationship management.

Claim: No competitive analysis provided.

Evidence: Author’s own account; no mention of other apps or platforms in this space.

Several risks and red flags emerge from the self-reported nature of the description:

1. No external validation or user feedback — The app exists only as described by one person.
2. Single-person development — No team, no product-market fit testing, no iteration history.
3. Privacy concerns — Reliance on private links instead of authentication or encryption.
4. Lack of monetization strategy — No indication of how the project will scale or generate revenue.
5. Unproven emotional utility — While emotionally compelling, there is no evidence that users find value beyond the author’s experience.

Inference: Without traction or feedback, it's unclear whether this product solves a real problem for others.

Inference: The app may not be scalable without additional features or team support.

1. Have you tested the app with anyone outside of your immediate circle?
2. What feedback have you received from users who tried it?
3. How do you plan to scale beyond a single developer?
4. Are there any plans for encryption or stronger privacy controls?
5. Do you have any intention to monetize or grow the product beyond personal use?