You’re absolutely right, SMS itself is commoditized, and there are many solid providers.
Console.text() isn’t trying to compete as “yet another SMS API”.
The focus is on developer ergonomics and intent, not transport:
one-line, code-level alerts (console.text("error"))
built for early-stage teams that don’t want to wire PagerDuty / Datadog yet
“Delivered” at the API level means the message was accepted by the downstream carrier / aggregator, not that it necessarily reached the handset. In some regions and carriers, especially for A2P traffic, messages can be filtered or silently dropped after that point.
we’re actively working on:
clearer delivery state distinctions (accepted vs handset-delivered)
fallback routing where possible
better guidance on sender IDs and content patterns that reduce filtering
If you’re open to it, sharing the country, carrier, and message type (transactional vs promo) helps us dig deeper.
ntfy.sh is great! But it requires:
- Setting up a topic/channel
- Installing their app on your phone
- Subscribing to topics
- Running a curl command or HTTP client
console.text() is:
npm install @holler2660/console-text
console.text('thing happened');
That said, ntfy.sh doesn't do SMS, so if you genuinely need to wake up at 3am for critical alerts, it's push notifications vs actual phone calls/texts.
The main thing I'm going for is ease of use
This is a pretty crowded space (Vonage, Clicksend, TopMessage, etc). They all provide very simple SMS sending libraries for JavaScript.
The biggest problem you’re going to have going forward is establishing trust over existing platforms.
You’re absolutely right, SMS itself is commoditized, and there are many solid providers. Console.text() isn’t trying to compete as “yet another SMS API”. The focus is on developer ergonomics and intent, not transport: one-line, code-level alerts (console.text("error")) built for early-stage teams that don’t want to wire PagerDuty / Datadog yet
It seems like my carrier is blocking the messages. The console says it was delivered, but my phone isn't getting anything.
“Delivered” at the API level means the message was accepted by the downstream carrier / aggregator, not that it necessarily reached the handset. In some regions and carriers, especially for A2P traffic, messages can be filtered or silently dropped after that point. we’re actively working on: clearer delivery state distinctions (accepted vs handset-delivered) fallback routing where possible better guidance on sender IDs and content patterns that reduce filtering
If you’re open to it, sharing the country, carrier, and message type (transactional vs promo) helps us dig deeper.
USA, T-Mobile, message was "Error Detected"
> Jason Goodison's YouTube video about micro-SaaS products
Can you link the video?
yup sure : https://www.youtube.com/watch?v=Bs29i2TR7AE
Why not use ntfy.sh?
interesting
btw - can't connect to any consoletext.dev domain - dashboard, docs, etc
[dead]
is this cloud-friendly? or just us-based?
It's global! The SDK works anywhere, and you can receive SMS to any phone number worldwide.