43 karma · joined June 19, 2013
Since I started my podcast go podcast() 3+ years ago everytime I'm saying to a guest that I'm blind and using a screen reader I always get the same reaction: "What, wow, I didn't know. I'd like to hear more about it".
I invited Ivan Fetch, a SRE that's also blind and we talk about challenges about being blind, not only tech-wise, but life also.
This will be a two part episode. I thought it might interest some people here in hacker news.
Thanks
I thought some of you might be interested in this episode. Fyne is an awesome Go project.
As a blind programmer using a screen reader daily I missed building desktop application. Almost sounds refreshing with the current "madness" of We these days.
I hope it's entertaining.
I launched Vivid in 2019, but it was not good timing. I even did not have a podcast at the time.
Today I'm the co-host of The SaaS Marathon podcast and going solo in go podcast(). I needed to generate clips myself, so I decided to relaunch the product beginning of January this year.
It's a tool that monitors podcast feed for new episodes and tries to pick what it thinks are the best moments. But, of course, it's straightforward to create manual segments as well.
You may edit the captions' text and customize the background image. Then clips are ready to be shared on social networks.
The goal of those clips is to allow more listeners and subscribers to find the podcast.
I'm currently trying to determine if podcasters out there find that idea exciting and would like to try the product. It's still in beta but working.
Any feedback would be greatly appreciated.
I'm switching my SaaS StaticBackend to an open-source model.
As a developer tool, I think it might have a better chance of getting initial traction as a fully open-source project. I picked the MIT license. I'm hoping to discover its actual potential.
I've built it with Go. It's a backend that handles user management, database, forms, and real-time communication.
My goal was and still is to have a lightweight Firebase without the vendor lock-in. Self-hosting the open-source version will enable total control over who owns the data and whatnot.
Any feedback is appreciated.
I can understand that and can see some kind of daily external backups of your data at some point. My whole goal is to make customers feel 0 pressure and especially about their data.
My goal with StaticBackend is to go more in dept in features like sending emails, Stripe payments. Features that a SaaS / web app typically need in the backend.
I'll not stop at Database and WebSocket. I'd like to go further based on demand. I'm building more a backend teamate for frontend developers.
I recognize that my choice of using a Document database instead of an RDBMS can be argued. But one as to make choices.
Thanks for your comment.
I think differently regarding self-hosting though. By the fact that StaticBackend is a Go web server, it's a standalone Linux binary and can be hosted very easily on x64 Linux server.
But I'll see when the first customer will choose that option. I'll be ready to help them deploy for sure.
My product is a database and websocket backend you can use from client-side, being web or mobile. It's a pieces of scalable infrastructure needed to build a SaaS or web application.
I realize that it's not very clear at this moment what it does, even to me to be frank. It's the infrastructure I need to build SaaS that compliment a Netlify app.
I admit that the 2. needs efforts on your part to switch. But it's possible to stop using the tool and still have no rewrite on your frontend code at all.
I'd called this: a SaaS backend API and infrastructure.
It would be a great companion to a Netlify application. Since they have hosting and function as a service. I think it would be the best fit for the current state.
- pricing: yes, seems like a recurring comments, but I want to make the leap between tier friendly, like Digital Ocean droplet for instance.
- the option to buy the source code is what makes this appealing compared to Firebase, where if you reach scale you have the option of paying 10k which is not huge if you're making 85k in MRR to get peace of mind and have full control.
- grammar: thanks, I'm not a native English that's correct, I'll try harder.
- pricing: My thought is that offering only 3 tier would be way too big of a leap from tier to tier.
- Firebase: I do have a fully disconected and local development server that helps during building phase. It's free, but I can see your point.
- vendo lock-in: My main objective is exactly that, to have an easy way to self-host and even get the source code once a product reach scale. Something that not much BaaS offer.
I'd like to request feedback on my product. I started building in last January with great momentum, but the pandemic made things a bit complicated.
As someone that built a dozen of SaaS in the last decades, there were some aspects of the backend I was bored of rewriting. User management is probably the major one.
I've tried Firebase and admit I found it interesting for 4-5 days, but as a Go backend developer, it did not suit my need/taste.
Why not try something just for me. At first, I called it "ezbackend" and built a dirty prototype in Node. I played with rewriting it in Go and started to like where it was headed. In January 2020, I thought that it might interest others, so I renamed the project, made it more rebust, and kept adding the minimal feature sets I personally wanted.
I'm now near the v1 / official launch, and I'd like to get some thoughts. I know it's not for everyone. To be perfectly honest, I'm not 100% clear who might be interested, but I'm excited enough to build side projects on top of it, it's enough for me to build it.
Any feedback is greatly appreciated.
https://store.dominicstpierre.com/build-saas-apps-in-go?coup...
I'm currently building another with that library.
It took me 11 months to write the book and source code that goes with it. Overall it was way tougher than what I thought it would be ;).
I've built two SaaS product with the same stack and technique since 2015, LeadFuze and Roadmap.
Hopefully, it helps some developers get started with Go for their side project.
If you want more background story, here's a small article linking to my visual disease.
https://dominicstpierre.com/see-your-stripe-mrr-and-monthly-...
Hah, so true. Although I find working for my startup more rewarding than trading hours for money.
My path is similar to yours, I quit my 9 to 5 job in 2007, started a software consultancy than moved to building my own SaaS in 2009. Since than, that's the only revenue for my family (2 daughters, wife, doing home school).
The stress and lower money at time for sure, but like others said, would not trade this to return in enterprise job.
Taking a couple of days out of the office to release some steam can work, but for me it was clear that this was not enough.
With the XYZ (Apple, Microsoft) stores these days I wonder if a $39-99 desktop software can truly have success on these compare the the average < $9 app.
High-end B2B software can certainly be profitable, I would guess the $500-2500 software coming with support, integration, training etc.
I completely agree with you on focusing on user feedback, I simply wanted a different, more quicker first impression homepage.