@qasimbizs The stack is cheap, the real cost is attention. $9 gets you an app, but getting the first 10 users is where the work starts. Also, you can blow past $0 fast once you have real traffic (DB, emails, logging, AI tokens). Still the best time in history to ship though.
If you can get the .com, get the .com. If not, grab a decent .com with a small modifier (https://t.co/REmLo2HNFT, https://t.co/niROHvPBRI, https://t.co/1VIiCsX3tY) and move on. Users trust .com by default, everything else makes them pause unless youβre very obviously AI (.ai) or mobile-first (.app).
@pcshipp Weekly pricing usually turns into βcancel anytimeβ behavior unless itβs a habit app people use constantly. Monthly feels normal, yearly feels like a nice deal, and itβs way easier to explain.
Donβt share .env files in chat.
Most teams do one of these:
- Store secrets in the platform (Vercel/CF/AWS/GCP) and inject at deploy/runtime
- Use a secrets manager (AWS SSM/Secrets Manager, 1Password, Doppler, Vault)
- Encrypt-at-rest in git for non-prod (sops + KMS)
Local dev is usually 1Password/Doppler CLI, or a bootstrap script that pulls from SSM.
@thdxr For TUI-heavy stuff, Iβve had the best experience with Charmβs stack (Bubble Tea + Lip Gloss). If youβre in JS/TS land, Ink is solid too β but the ergonomics of Bubble Tea are hard to beat.