The Shopify Goldmine: How to Build Your First App in Rails
If you know Ruby on Rails, you are already sitting on a goldmine.
My thoughts on Web Developing, Solopreneurship, Linux and other. Including notes to myself for easier and quicker developing.
If you know Ruby on Rails, you are already sitting on a goldmine.
For a long time, if you wanted to send a “Push Notification” to a user’s phone or laptop, you needed a native mobile app. For solo developers, this was a huge barrier. We had to rely on emails that nobody reads or expensive SMS services.
If you have been using AWS S3 for your Rails file uploads, you know the pain of the monthly bill. It’s not just the storage cost; it’s the Egress Fees. Every time a user downloads a file or views an image, AWS charges you for the data leaving their servers.
Imagine a user trying to upload a 100MB video or a high-resolution photo to your app. If you use the standard Rails file upload, that file travels from the user’s browser to your Rails server, and then your server sends it to S3 or Google Cloud.
I’ve lost count of the number of hours I’ve spent in the past building “Live Search” features.
I am a huge fan of Hotwire. It’s what allowed me to stop writing massive React apps and go back to enjoying Ruby. But recently, a new player has entered the “Hypermedia” world that every Rails developer should keep an eye on: Datastar.
I love Ruby. It is the language that made me happy to write code. But as a Rails developer, I eventually hit a wall. Maybe I needed to process a 2GB CSV file, or build a real-time notification service that handles 10,000 connections.
If you spend any time on Tech Twitter lately, you might feel like the sky is falling. People are saying that “coding is dead” and that AI will replace every developer by 2027.
I remember when I first started learning Ruby outside of Rails. I was building a small script, and my code kept crashing with NameError: uninitialized constant. I was so confused because I knew the file existed. I realized that in plain Ruby, you have to manually add require './user' at the top of every single file.
If you have ever used the Stripe API, you’ve noticed their IDs look awesome. Instead of a random number or a long, confusing UUID, they look like this: cus_M1p7abc123 or ch_3Oixyz456.