🧾 New Reading
⌄
Off
Voice status: Ready. If voice fails offline, use the keypad below.
Tip: Some Android browsers require internet for speech-to-text. If you opened this as a file, try hosting it (HTTPS or localhost).
Tip: Some Android browsers require internet for speech-to-text. If you opened this as a file, try hosting it (HTTPS or localhost).
Hands‑free: After a voice save, the app asks “Add another?” — say yes or no.
If your browser can’t speak prompts, it will still listen and you can continue by tapping Start Voice.
If your browser can’t speak prompts, it will still listen and you can continue by tapping Start Voice.
Manual keypad (offline-safe): Tap digits to fill the Glucose box.
⚙️ Preferences
⌄
Note: This app stores data locally in your browser (localStorage). Export JSON for backups.
🆘 Help & Troubleshooting
⌄
Why “Start Voice” may not work
Voice-to-text in this app uses your browser’s built-in speech service (Web Speech API). Whether it works is controlled by your browser, permissions, connection/security, and sometimes your network environment.
Voice-to-text in this app uses your browser’s built-in speech service (Web Speech API). Whether it works is controlled by your browser, permissions, connection/security, and sometimes your network environment.
1) Microphone permission (most common)
If permission is denied, voice cannot start.
Android: Settings → Apps → (your browser) → Permissions → Microphone → Allow.
Browser: tap the lock icon → Site settings → Microphone → Allow.
If permission is denied, voice cannot start.
Android: Settings → Apps → (your browser) → Permissions → Microphone → Allow.
Browser: tap the lock icon → Site settings → Microphone → Allow.
2) “file://” mode vs HTTPS/localhost
Some browsers block or break voice-to-text when the page is opened as a local file (file://).
Best fix: open via HTTPS (on your website) or run via localhost on a PC.
Some browsers block or break voice-to-text when the page is opened as a local file (file://).
Best fix: open via HTTPS (on your website) or run via localhost on a PC.
3) Secure context requirement
Many browsers require a secure context for microphone features: HTTPS (or localhost). If you are on plain HTTP (not localhost), voice may be blocked.
Many browsers require a secure context for microphone features: HTTPS (or localhost). If you are on plain HTTP (not localhost), voice may be blocked.
4) Offline voice-to-text
Some Android browsers use an online speech service. If you are offline, you may see a network error.
In that case, use the manual keypad (works 100% offline).
Some Android browsers use an online speech service. If you are offline, you may see a network error.
In that case, use the manual keypad (works 100% offline).
5) Firewalls — can they affect voice?
Usually: a firewall does not block the microphone itself (that’s controlled by permissions).
However: if your browser’s speech recognition relies on an online service, a firewall or network filter can block the required outbound connection and cause errors like network or service-not-allowed.
Examples: corporate/school networks, strict router filters, VPNs, security apps, or DNS filters.
What to try:
Usually: a firewall does not block the microphone itself (that’s controlled by permissions).
However: if your browser’s speech recognition relies on an online service, a firewall or network filter can block the required outbound connection and cause errors like network or service-not-allowed.
Examples: corporate/school networks, strict router filters, VPNs, security apps, or DNS filters.
What to try:
- Test on a different network (mobile data vs Wi‑Fi).
- Disable VPN temporarily and retest.
- Check router/firewall “content filtering” / “safe browsing” / DNS filtering settings.
- Try Chrome on Android, and ensure mic permission is allowed.
Quick status check
The mic indicator near “Start Voice” shows: Off, Starting…, On, Yes/No…, or Error. If it never leaves “Starting…”, it’s usually permissions or browser blocking.
The mic indicator near “Start Voice” shows: Off, Starting…, On, Yes/No…, or Error. If it never leaves “Starting…”, it’s usually permissions or browser blocking.