E7: From Building to Marketing

07/22/2024, duration: 15:18

Video

Transcript

Welcome to Debugging Dan, where I share weekly my journey, balancing life, a full-time job and side projects. I'm Dan, your host. Let's dive in. The topic I'd like to talk about today is from building side projects to marketing them. This episode will contain a bit of history about me and my experience leading up until now.

So I'm a developer. I've been developing applications for over 20 years, both professional and for my job, where I'm also working for 20 years, but I've been doing programming longer than that. And what I did in those 20 years for side projects is I would be building things for personal use, interesting stuff that solved the problem for me at the moment or doing some experimentation. And after a while, I would abandon those projects and later on start a new one. The benefit for me was that every project would allow me to experiment with new technologies or a new tech stack or reusing the old one.

By starting a new project every time, I wouldn't have the technical debt of staying in the same project for a while and having to work with previous decisions by me and working with them. So I did start working on a RSS reader four or five years ago. And there I took the first steps to trying to build something that other people would also use. So, uh, it, it started as an RSS reader. So for news sources, but it did not only import RSS. It only did, it also did Twitter and other social, social networks so that I would have one source where I would be reading news and other interesting things all in the same, um, scope.

So what I initially did is the build it and they will come approach. So there are different approaches to, um, to building projects or marketing them. But one of the most naive ones is just building it, putting it out there and expecting people to find your project and using it. And at that time I did realize build it and they will come, did not really work because I was not that naive that I thought that people would automatically find it and use it. But I figured, Hey, I'm building something, I'm using it myself and as an added bonus, maybe some other people would also find it or use it, but besides some signups from bots, nobody found it and nobody used it.

So I did realize for something to really work, you really need to actively, uh, go out and find, uh, people that like to use the thing that you're building. And at some point I changed the project and, uh, because initially I built it to support multi-user, uh, and at some point, uh, I was hosting it on a Raspberry Pi and it was having some resource issues. So I rewrote the project and making it only work for one user without having to log in, just having it open to allow it to have more resources and uh, work better on the Raspberry Pi.

At some point, I even bought a domain name for it. I called it, uh, a ferret feed, uh, initially I thought I would call it media feed because it was a feed of media posts, but that was already taken. So at some point I figured maybe I need to do something with a mascot. It's privacy badger has a badger for an icon that's a browser extension. And so I figured I do a ferret and that allows me to use the power of a ferret as a logo. And, um, I, I bought a domain, I had it for a year, but now I have it running, uh, just on a, on a subdomain of my current domain and only use it myself.

That was the first project I really did something. After that, I started on a project that I called WALL-E, uh, inspired by the robot from the Disney movie WALL-E. I bought a small 3.5 inch screen that worked with a Raspberry Pi. And I hung that screen up somewhere in the house. Uh, and I built a bit of software that would allow you to display a photo gallery or the weather or similar things on that display. I'm also inspired by the magic mirror software.

And that project eventually involved to Teletron, a project that I'm still currently actively developing. I built it and I also created an extension or a plugin platform, so you could set up your own instance and have your own extensions. Uh, if you're curious about it, you can find it on teletron.me. I, for that project, I have now kind of like 50 signups, but most of them seem to be bots or, and they are, there are a lot of, uh, Russian email addresses there and they're not actively using it.

Uh, every time I, I, um, I create a custom or personal welcome message, but nobody put them out has responded to the, um, to the welcome message. Then I figured, Hey, I want to do more marketing. I want to make me available, but I also want to know how I'm doing. So I figured I'd build a call called Reslytics, which was, is a tool to track social media metrics. So it would read data from social media.

It would use the Twitter API, which was then still free to track the count of the follower count, the like count for an account. Uh, but for individual tweets, it would also track how many times it was clicked, how many retweets, how many replies. Um, but the same also for GitHub repository NPM packages. So you would get one system where you would get analytics for all the stuff that you're publishing out there. I did build it and I really enjoyed building it. And for that product, I've started a boiler plate thing.

So I built a lot of things there for the first time, like, uh, integrating login, password resets, but also having a price plan integration with Stripe. But no, the integration with Stripe was later. So initially I built it as kind of a better platform saying, Hey, you can use it now, but it's in beta. And at some point you need to pay so that I didn't have to do the Stripe integration yet.

I, it was fun to build, but at some point it stagnated because I needed to finish it. I wasn't still really happy with the design and the enthusiasm kind of faded away. Also because completing something or a side project is often the hardest thing to do. You get at some point you did all the fun stuff and then you need to build the more boring stuff like payment integration or management things.

Um, and so for me, that kind of faded away, but the good thing that came out of it was the boiler plate. And later on, I rebranded it in terms of name to watch your numbers. So that was an idea from my wife. So Reslytics is not really a, a, a good name doesn't really tell you what to do. I didn't buy that domain. Even while I suggested watch your numbers because you're gathering analytics, you need to watch your numbers basically.

So I did purchase the domain. I still have that. And currently I've been building it again, rebuilding it to allow you to gather data from multiple sources, but then not social networks, but just, uh, Jason or, uh, my SQL databases and do queries there, generate reports and share those with other people. Uh, that's what I'm currently working on. It's not live yet, but that's also something that I want to use myself to gather the podcast analytics from different sources and automatically send that to that to me on, uh, on a Friday or Saturday morning, for example.

So I can have a look at it and I am actively, um, forced to, to view it. So that was what's your numbers that I I'd worked on. And, uh, so I also implemented some open source development tools and libraries. So I built super safe, I built that part of Wally, I believe to have, and that allows you to easily have a database and also a API on top of that database using SQLite or my SQL. I use that for all my projects. It's pretty mature. It works, it's not built to for large volumes of people.

So it's not very efficient, but it does work for smaller numbers and it makes it very easy to set up an API. On top of that, I built super safe auth, which builds user authentication and protection on top of super safe. So I implemented the hook system and the super safe auth package adds the user ID to every record that you write when returning data or querying data. It will also require the user ID to be set.

So it would only return the records for that specific user. And that's more of a fun project. I'm not monetizing that or actively, uh, marketing that it's just something that I use myself. It's open source. It's on GitHub on NPM. It's just there. And for me, looking back at all those projects, I find that marketing for me is the most challenging part. And it's not necessarily marketing, but also getting stuff out there and getting it known.

So I really enjoy building. I'm a developer and I'm having difficulties completing the last 10, 20% of a product and having a plan to get that out there. So I'm more focusing on purity building and I need to focus more on marketing and sharing. And one of the things, and that's also the reason that I started this podcast is to have more of a social media presence and not the, uh, the many Twitter bots or Twitter people that try to gamify Twitter.

And just hack the algorithm or I'm trying to be there, but also be there genuinely, genuinely, just be myself, send messages there. And that's proven to be difficult because I'm not really, I'm often not in a mindset to share things on Twitter or other, uh, social media and also interact with other people on it. Cause I'm often more focusing on other things I am winding down from a long day at work and I don't have the energy to, to really actively, uh, pursue other things on social media.

So I told you about, uh, projects in the past. My focus currently is ObserverLize, which I completed a pivot. So at some point I realized for Teletron and for ResLytics that I also wanted to know how people were using the application. So I started doing ObserverLize, which is a kind of an analytics platform, but focused on SaaS. So you have a SaaS or a product and you want to get insight in how users are using your SaaS.

The pivot that I did there is initially, it was just sending, uh, keys of pages that were visited, active activities that were done to ObserverLize. And I didn't realize that at the time, but it was just still just an analytics platform. It didn't really add anything on top of that. And it was mostly, what it was mostly doing in its MVP version. So, uh, minimal, minimum valuable product is that it was showing, uh, tables and tables of data.

It wasn't, uh, generating insights. At some point I had a ID to add gamification to it. So use the events to generate badges, complete tasks, track counts of things. So use that for gamification and to allow people or to, um, invite people to use the product longer, to engage them longer with the, with, with the product, not ObserverLize itself.

With the product that uses ObserverLize and, uh, there I really forced myself to, to, to make that pivot, complete it. And I also even created a small marketing plan on how to market it after that. I haven't really started on marketing yet. I, I feel like I'm postponing that and, um, procrastinating with implementing small other products, like, uh, restarting on watch on numbers and, uh, some, uh, to do app that I was doing for myself with, with notion, also starting this podcast, it's kind of taking away from the marketing on ObserverLize and at the moment, that's, that's okay. I'm okay with that.

So I started this, this podcast, as you mentioned early, earlier, and I also want to use that as a mechanism for doing accountability. So the things that I say on and do for this podcast, I have a feeling that when I put it out there, I'm kind of promising myself and other people. I know I'm promising other people things, and I hope that helps me in feeling more pressure to do the things that I promised and I say, because I'm also letting other people down instead of just doing it for myself.

So I'm hoping that will work. Also, I'm hoping on getting feedback from the people that are listening to this podcast, if there are any people listening, because I need to do more marketing. Um, let me know if you're listening, you can listen on YouTube, you can listen on other podcast ops. I'm still working on getting it to work on Apple, but I did hear from them on what I need to change. So there has been contact, so that that's hopefully that works.

What I do feel is that I'm currently balancing multiple projects for me that helps because, uh, my mind doesn't really like being focused on one thing for a long time. So I'm handling multiple projects. And then at some point when one of those projects is gaining more traction, I would focus more on that specific project if needed, try to grow it, get more users. And hopefully I would need, uh, I'm at some point, I'm able to gain income from my side projects to get an additional income from those side projects instead of only doing them for fun.

I hope to get a little bit back from them for this podcast and also from YouTube. I'm also learning new skills. So I like that I'm learning how to do a podcast. I'm going to learn how to do video content, hopefully in the short term. Oh, uh, I hope to start somewhere in September with that. So I have the time to learn from that and also do this podcast via a video, something that I'm hoping to learn.

And for me, doing side projects is mostly about getting to know with new technology, uh, solving problems for myself. And, um, that's for me important in a side projects. And in the past few years, I've been trying to, as an added bonus, have other people also benefit from what I'm building. I'm trying to solve a problem that I think other people will also have. And now I'm taking the step to bring the product that I built or the thing that I built to other people, hopefully have them see that, Hey, this is also solving my problem.

Interesting. Let me have a look at that. Thanks for tuning in to debugging the end. If you enjoyed this episode, please subscribe and leave a review. Stay curious and see you next week.