docs: define free and paid product model
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- payments
Research direction
The issue names no files, tests, or entry points. Start by identifying where product limits and entitlement decisions belong, then define the free and paid rules, offline and account-lifecycle behavior, and the boundary with ChatGPT access; done means the model is documented and the acceptance criteria are unambiguous.
Written by the indexing model from the issue text.
Description
Objective
Define a simple monetization model without weakening the core product or creating confusing limits.
Proposed initial model
Free:
- Queue up to 2 prompts total, meaning one automated follow-up after the initial prompt.
- Local-only operation.
- Core queue controls.
- No ads.
Paid:
- Larger or unlimited queue sizes subject to practical safety limits.
- Advanced queue features added over time.
- Optional workflow features.
- Optional cross-device sync only if a backend is introduced later.
Important product rule
QueueIt sells the QueueIt software and workflow features. It does NOT sell ChatGPT access, model tokens, or a way around ChatGPT usage limits.
The extension must never imply that paying QueueIt increases a user's ChatGPT quota.
Entitlements
Document:
- anonymous/free state
- paid state
- how entitlement is checked
- what happens offline
- grace period behavior
- account deletion
- refunds/cancellation handling
- server-side verification if a backend is introduced
Recommendation for MVP
Do not build payments before the core queue loop is stable. First validate the product with a local free version.
Acceptance criteria
A user can understand the free limit in one sentence, and paid functionality is clearly separate from ChatGPT subscription access.
- Dominant language
- CSS
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ChinmayOnGithub/queueit
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ChinmayOnGithub/queueit#10 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in ChinmayOnGithub/queueit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cline/mcp-marketplace#2723 ·
-
Razorpay overrides woocommerce_thankyou_order_received_text for ALL payment gateways (including COD)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
razorpay/razorpay-woocommerce#672 ·
-
broker bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
marketcalls/openalgo#2151 · 2 comments ·
Maintainers usually reply within 1 day
-
bug contract difficulty: easy
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MetroLogic/fluxapay_contract#898 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
fossasia/eventyay#6019 · 1 comment ·
Maintainers usually reply within 1 day