1
1 Comment

Remember when getting a phone number for SMS development was fast and easy?

Getting an SMS phone number for your projects used to be a quick and easy process. I could grab a number from Twilio in seconds and get straight to integrating SMS into my apps.

But now, it's a nightmare. There are so many regulations, and I find myself answering a million questions about why I need the number and how I’ll use it. It’s such a hassle just to get a number for development and testing.

This frustration led me to create my own API that turns an Android phone into an SMS gateway. I've been using my solution for months now, and it works great. It simplifies the whole process and saves a lot of time.

I figured other developers might enjoy using something like this also, so I decided to share my solution with everyone by creating Txthis.com.

Has anyone else been dealing with this? How are you navigating these SMS regulations?

posted to Icon for group Building in Public
Building in Public
on July 31, 2024
Trending on Indie Hackers
Your build-in-public audience is not your market. I learned the difference the slow way. User Avatar 257 comments Most founders don't have a product problem. They have a visibility problem User Avatar 61 comments Day 4: Why I Built a $199 Workspace Nobody Asked For User Avatar 40 comments How to automatically turn customer feedback into high-converting testimonials User Avatar 39 comments Built a "stocks as football cards" thing. 5 days in, my launch tweet got 7 views. What am I missing? User Avatar 34 comments Spent months building LazyEats AI. Spent 1 day realizing I have no idea how to get users. User Avatar 29 comments