GrowVPD Pro is built by a small team of grower-engineers who care more about quality than ship-anything-fast. We’re currently in late beta — the core works, but we’re still polishing every device integration, every UI flow, every translation. This guide explains exactly what “beta” means for us, what we ask of you, and what you get out of being here early.
On this page
1. Honest framing
We’re a small indie team. Two engineers, one designer, occasional help from a translator. We’re self-funded, which means every feature we build either solves a real growing problem or it doesn’t happen. There’s no marketing budget, no growth-hacking team, no VC pressure to ship half-baked shiny things.
What that means for you:
- Bugs reach us within hours and ship fixes within days, often same day.
- Features get prioritized by how many real growers are blocked by them, not by what looks good in a demo.
- You can talk to the actual people building the app, not a tier-1 support agent reading a script.
- If you have a cool idea, we’ll consider it for the next sprint — not the next quarter.
The flip side:
- You’ll find rough edges. A button that doesn’t do what you expect. A device our test rig hasn’t exercised yet.
- We don’t have a 24/7 support desk. If something breaks at 3am, we’ll see it in the morning.
- Translations are still being polished for some languages. If you’re native speaker and spot something off, please tell us.
If you want a polished commercial product and you don’t want to be involved in shaping it, this is probably the wrong moment to join. If you’re curious about being early to a tool that could become the standard for grower automation, you’re in the right place.
2. What “beta” means here
The beta label gets thrown around loosely. Some companies call it beta forever (looking at you, Gmail circa 2010). Others call it production from day one and have you find the stack traces. Here’s where we actually are:
| Aspect | Status | Notes |
|---|---|---|
| Core VPD calc + chart | Stable | Used in production by 600+ growers since 2024 |
| Diary + photo timeline | Stable | 200K+ entries logged across users |
| Tuya LAN control | Stable | Audited against reference implementace, tuya-local, LocalTuya code |
| Tuya Cloud Bridge | Stable | 5-step wizard ships in 1.0; OAuth pending Tuya partnership |
| Mars Hydro / AC Infinity / Spider Farmer / Vivosun | Stable | Verified against own and community hardware |
| Bluelab / SANlight | Beta | Less hardware in our test rig; community help speeds it |
| Multi-device sync (Ed25519) | Beta | Works LAN; cloud relay shipping next sprint |
| Hub Mode (24/7 phone) | Beta | Works on Android 7+; foreground service tested for weeks |
| iOS app | Late alpha | Feature-complete, edge cases still landing |
| Climate Intelligence engine | Beta | VPD, energy, predictive analysis — tuning in progress |
| Disease detection | Beta | Advanced on-device scanner; precision improving with examples |
If you’re unsure whether something is stable or beta in your specific setup, just ask in Discord — honest answers within an hour during EU daytime.
3. How to join
Three steps. Costs nothing.
- Install GrowVPD Pro from the Play Store (Android) or join the iOS TestFlight (link on the homepage).
- Use it for a real grow. Doesn’t have to be elaborate — even one tent with a TH sensor is plenty.
- Join Discord at discord.gg/BGDpE6nP and say hi in
#introductions.
That’s it. No NDAs, no application form, no waitlist. We don’t gatekeep beta — the more eyes on the app, the faster it improves.
4. Where we hang out
Real-time chat, screenshots, voice if you want it. #bug-reports for issues, #cloud-bridge / #mars-hydro / etc. for device-specific help, #feature-requests for ideas. discord.gg/BGDpE6nP
Some growers prefer Telegram. We mirror major announcements there. Less granular than Discord but a good way to follow.
For private feedback or anything you don’t want public. We answer within 24 hrs (often the same day in EU).
Long-form feature discussions. We use it for design RFCs that benefit from threaded conversation. Linked from the guides hub.
5. What we ask of you
Beta isn’t a passive freebie — it’s a collaboration. We can’t make the app good without your input. Here’s what genuinely helps:
- Real-grow feedback. “I tried the auto-stage detector during my flip; it suggested early flower 3 days late. Photos attached.” That’s 100x more valuable than “the UI is confusing” (though both help).
- Screenshots when you report bugs. A screenshot, the device list, the OS version, what you were doing — we can repro in minutes instead of hours.
- Suggestions with context. “I’d love a feature where X because in my setup Y.” Tell us the why; we’ll figure out the what.
- Device IDs. If your Tuya/Mars Hydro/whatever device isn’t in our compatibility matrix, send us the product_id (Settings → Connected Accounts → tap device). We add it to our test plan.
- Translation polish. If you’re native in CS / DE / ES / NL / FR / IT / PT / PL / TH / HE, we’ll happily fix any clunky phrases you spot.
What we don’t ask: that you become a power user, that you write detailed reports, or that you have a specific number of tents. Even “I tried it for 30 minutes and bounced because of X” is useful feedback.
6. What you get (during beta)
- Free Pro features until v1.0 ships. Currently includes BLE sensor, Smart Automation, Disease Detection, Export, Photo Privacy, Templates — all unlocked.
- Direct line to the team. The two engineers building the app are in
#general. Ping@devfor anything urgent. - Roadmap visibility. What’s shipping next, what we’re debating, what we just rejected. We post sprint summaries every 2 weeks.
- Early features on a feature-flag basis. You see things weeks before public release if you’re willing to test rough edges.
- Hardware compatibility input. If your device isn’t supported, we prioritize based on community demand. Active testers move things up the queue.
7. Perks at GA launch
When we hit 1.0 (target: Q3 2026), beta testers who’ve actively contributed will get tangible thank-yous. We don’t want this to feel transactional, but we also know your time has value:
Lifetime Pro for active reviewers
If you’ve filed at least 3 substantive feedback items (bugs, suggestions, screenshots) before GA, you get a one-time Lifetime Pro license. $49.99 $29.99 — or just free if you’ve been particularly involved.
Early access to ESP32 BYOD bridge dongle
We’re prototyping a $25 ESP32 dongle that gives you a local hub without needing an old phone or RPi. Beta testers get first orders + the dev kit firmware before public release (target Q4 2026).
Vote on roadmap priorities
Quarterly roadmap surveys go out to active testers. Your votes weigh heavily in what ships next. We don’t pretend to be a democracy, but you’re materially closer to the decisions than a regular customer.
Name in the credits screen
If you want it. Some people don’t (privacy). Those who do get listed in Settings → About → Beta testers, alphabetical, with optional Discord handle.
8. Release cadence
We ship in two-week sprints. Each sprint:
- Day 1: planning, picking the highest-impact items from feedback + roadmap
- Day 1–10: build, test, dogfood
- Day 10–13: internal QA on real grow rigs
- Day 14: ship beta to TestFlight + Play Store internal channel
- Day 14+3: promote to public if no critical issues found in 72 hr
If a critical bug surfaces at any point, we hotfix within 48 hr. The release notes (in-app: Settings → What’s new) explain every change, including the not-fun ones like “fixed unicode crash on Polish locale”.
9. Different tester levels
Not everyone wants the same level of involvement. Choose your fit:
| Level | What you do | What you get |
|---|---|---|
| Casual | Use the app, occasionally chat in Discord | Free Pro until GA, see updates |
| Active | File 3+ bug reports or suggestions per quarter | + Lifetime Pro at GA, name in credits |
| Hardware tester | Have a device we don’t own, willing to test it for us | + Direct dev pairing for that device, faster integration |
| Advocate | Make YouTube videos, blog posts, or recommend on forums | + Affiliate commission (15% on referred subscriptions), early hardware |
| Translator | Native speaker willing to polish strings | + Listed prominently in language credits, beta access to localizations |
You can move between these freely. No commitment, no contracts.
10. FAQ
Q: Will my beta data carry over to GA?
Yes. Your diary entries, grows, photos, automation rules — everything stays. We never wipe data between versions. If we ever did need to migrate something fundamental, we’d announce 30+ days in advance with full export support.
Q: Is the beta safe to use for an active grow cycle?
Yes. We dogfood with our own grows; if it works for ours it works for yours. The bugs you might hit are in UI polish or device-specific edge cases, not in the core diary or VPD logic. That said, if you’re running a commercial-scale operation where downtime costs you money, talk to us first — we’ll give you a stable channel and direct hotline.
Q: How is privacy handled for beta diagnostics?
Crash reports are opt-in (Settings → Privacy → Crash reporting). When enabled, we get stack traces and OS info — no diary content, no sensor readings. You can opt out anytime; doing so doesn’t affect anything else.
Q: What if I find something wrong but don’t want to use Discord?
Email support@growvpd.pro. We answer everything. Discord is faster and gets community input, but email works fine.
Q: When does GA / 1.0 ship?
Target: Q3 2026. We won’t ship until major device integrations have stable real-grow signals from at least 50 distinct testers per platform. We’d rather ship 6 months later and have it work than ship on a date and have it embarrass us.