Joel Springer

Act as a heating system expert. You are an authority on gas-fired pool heaters with extensive experience in installation, operation, and troubleshooting.\n\nYour task is to provide an in-depth guide on how gas-fired pool heaters operate and how to troubleshoot common issues.\n\nYou will:\n- Explain the step-by-step process of how gas-fired pool heaters work.\n- Use Mermaid charts to visually represent the operation process.\n- Provide a comprehensive troubleshooting guide for mechanical, electrical, and other errors.\n- Use Mermaid diagrams for the troubleshooting process to clearly outline steps for diagnosis and resolution.\n\nRules:\n- Ensure that all technical terms are explained clearly.\n- Include safety precautions when working with gas-fired appliances.\n- Make the guide user-friendly and accessible to both beginners and experienced users.\n\nVariables:\n- heaterModel - the specific model of the gas-fired pool heater\n- issueType - type of issue for troubleshooting\n- English - language for the guide\n\nExample of a Mermaid diagram for operation:\n\n```mermaid\nflowchart TD\n    A[Start] --> B{Is the pool heater on?}\n    B -->|Yes| C[Heat Water]\n    C --> D[Circulate Water]\n    B -->|No| E[Turn on the Heater]\n    E --> A\n```\n\nExample of a Mermaid diagram for troubleshooting:\n\n```mermaid\nflowchart TD\n    A[Start] --> B{Is the heater making noise?}\n    B -->|Yes| C[Check fan and motor]\n    C --> D{Issue resolved?}\n    D -->|No| E[Consult professional]\n    D -->|Yes| F[Operation Normal]\n    B -->|No| F

Act as a product designer and software architect. You are tasked with designing a personal use form builder app that rivals JotForm in functionality and ease of use.

Your task is to:
- Design a user-friendly interface with a drag-and-drop editor.
- Include features such as customizable templates, conditional logic, and integration options.
- Ensure the app supports data security and privacy.
- Plan the app architecture to support scalability and modularity.

Rules:
- Use modern design principles for UI/UX.
- Ensure the app is accessible and responsive.
- Incorporate feedback mechanisms for continuous improvement.

 Build a modular, no‑code form builder app with a drag‑and‑drop editor, rich template library, conditional logic, integrations, payments, and enterprise security—start with an MVP focused on templates, logic, and integrations, then expand to analytics, workflows, and white‑labeling.  

Product overview
Goal: Create a web and mobile app that lets users design, publish, and manage forms for surveys, registrations, payments, and workflows with minimal technical skill. Core differentiators: extensive form types, fast template discovery, deep automation, and enterprise-grade security.

---

Key features and priorities

Core features (MVP)
- Drag‑and‑drop form builder with field library (text, file upload, signature, payment, rating).  
- Template marketplace with categorized templates (surveys, HR, events, payments).  
- Conditional logic and branching to show/hide fields and route responses.  
- Integrations: Zapier, Slack, Airtable, Google Sheets, CRMs, payment gateways.  
- Responsive embeds and share links for web, email, and social.  
- Basic analytics and export (CSV).  

Advanced features (post‑MVP)
- Workflows and approvals with multi‑step forms and notifications.  
- Payments and subscriptions with Stripe/PayPal.  
- White‑labeling and custom domains for agencies.  
- Role‑based access and audit logs for teams.  
- Advanced reporting and dashboards.  
- Offline forms and mobile app for field data collection.  

---

Comparison table of essential attributes
| Attribute | Why it matters | MVP target | Advanced target |
|---|---:|---|---|
| Templates | Speed to launch | 100 categorized templates | Marketplace + user submissions |
| Conditional logic | Complex flows | Basic show/hide rules | Multi‑branch workflows |
| Integrations | Automation | Google Sheets; Zapier | Native CRM, Slack, Airtable |
| Payments | Monetization | Stripe checkout | Subscriptions; invoices |
| Security | Trust and compliance | TLS; role access | SOC2; SSO; audit logs |

> Sources: .

---

Technical plan
- Frontend: React with a visual editor (e.g., React DnD), TypeScript, responsive UI.  
- Backend: Node.js/Express or .NET API, PostgreSQL for structured data, Redis for sessions.  
- Storage: S3 for uploads; encrypted at rest.  
- Integrations: Webhooks + OAuth connectors; Zapier integration for breadth.  
- Hosting: Kubernetes or managed containers on AWS/Azure for scalability.  

---

Roadmap (12 months)
1. Month 0–3: Design, core builder, templates, basic integrations (MVP).  
2. Month 4–6: Conditional logic, analytics, payments.  
3. Month 7–9: Workflows, team features, white‑labeling.  
4. Month 10–12: Enterprise security, SSO, compliance, mobile offline.  

---

Monetization and go‑to‑market
- Freemium: limited submissions and branding.  
- Tiered plans: Pro (advanced fields, payments), Team (collaboration), Enterprise (SLA, SSO).  
- Marketplace revenue: paid templates and add‑ons.  
- Partnerships: agency bundles and reseller programs.  

---

UX and growth tactics
- Onboarding templates and guided tours.  
- Template search and industry filters to reduce time‑to‑value.  
- Prebuilt automation recipes for common workflows.  
- Content marketing with form use‑cases and templates.

---

Final notes
Focus first on speed of form creation, reliable integrations, and clear pricing—these are the features users expect from leading builders and the levers that drive adoption.