I earn $4'760 month from side projects with this Simple tech stack

- Speaker A tells the audience that he earned $4,470 from his side projects with simple tech stack in the last month. The income is almost passive. - In this video, the developer explains the tools he uses to make successful mobile applications and start earning money from the app store. He introduces Swiftui, Astro, and Wishkit. - Telemetry desk is very easy to implement and it provides information about active users, devices, iOS versions, etc. It helps to get better analytics and it helps to build paywalls. Revenue cat is another important tool in the tool set.

In the last month I earned $4,470 from my side projects with simple tech stack you can learn in a month. Let me show you. So this income is from August September data is still coming but I will be honest with you, that will be a little bit less. But yeah, this income is almost passive and I'm spending just few hours in a week updating apps, fixing some bugs and experimenting with paywalls. In July it was more in September when months will be finished it will be less because I experimented with my paywalls and a little bit hurt my sales. I'm often asked what background I use and which architectures I'm using. So in this video I'm going to show you all the tools you need to make successful mobile application and start earning money from the app store. First that I'm using, that is Swiftui. In all my indie applications I am using Swiftui for programming. And yes, Swiftui is production ready. Stop asking. Swiftui versus Uikit if you are building indie applications, you can build them using Swiftui. If you are saying that oh, it is not possible to make fancy user interface, it is. This is pure Swiftui. Just take a look on those titles, how they are kind of moving up, hiding and so on. Also the picture kind of moving around all of that is just pure Swiftui without any additional libraries, nothing. So you can make good looking, stable applications and that will work just fine. Okay, that's not Swiftui. So yeah, I am actually besides working on my side projects, I'm also running community for indie app developers. I am working full time hours as iOS consultant. I just don't have time to work full time on the applications. But yeah, Swiftui open Apple documentation, start learning. That's the first thing you should learn. Next one that I'm using often, not every day, but very often. That is Astro application. Astro application is for keywords. Whenever I have new Apidea in mind, I am opening Astro application and starting to do research for keywords. The Astro app currently as I know is one of the best price performance features kind of value in the market and you are getting unlimited keywords. You can do research. I have hundreds of keywords and in other apps you how to pay, bye app number that you are adding or keywords and that is limiting factor in other applications. In this one I like that I don't have those limitations. Okay, another one, not programming tool but necessary is Wishkit library. Wishkit kind of helps you to build those. Let's say if you will go in the settings of my application you can see feature requests and that is nice way to get feedback and feature requests from the users to understand what they like, what they don't like and so on. And there is basically backend and user interface for that as well. So you basically see for what features users are asking and you have to approve them before if someone just spamming you with some random stuff make bad, you just ignore them, you know. So yeah, Swiftui will help you to build user interface. Astro will help you to rank in the app store. Wishkit will help to get feedback from users, but you probably will need one more component. You will need data persistence. You have to save users data. And yes, you can save a little bit in user defaults like user settings and so on. Let's do not go deep in those things, but you need something more. And for something more, I historically used Realm database and that's that realm database and the integration for it and syntax is very simple, very easy to use. And I started to use back in the days when Coredata was another kind of option. And yeah, realm was just much, much more easy to use. And I still have it currently in some projects as a legacy. In this one, for example, I have a realm database and it still works just fine. But today in new and upcoming applications I am starting to use Swift data. It is way more easier to use comparing with Coredata back in the days. So if you are using SwiftuI, use Swift data to save users data and also by adding cloudkit, which is easy task to do, you will have data synchronization in between applications. So if user will have, let's say app on iPhone and on iPad, and maybe you allow it to install it on Mac as well, all the data will be synchronized in between devices. If user will delete the application, install it again, that data is still connected to this user iCloud account. So you have data persistence without needing to add authorization, like, I don't know, Firebase or super base needs and so on. And you for many cases can live without kind of real backend. And that's my answer to the question, what backend do I use? I am trying to avoid backend in my indie apps as much as possible, and my indie apps are relatively simple and I can live without backend. And yeah, I have more than one application in the app store. Let me see, here are a few apps that I removed by myself, but there are plenty of apps which are still up and running and I do not use currently anything else but Swift data, Cloudkit or realm. So that's my suggestion for you as well. If you are starting, try to keep it simple. Do not try to learn back end development and so on. Build apps offline first and that will be easier for you. Okay, telemetry desk, that is next tool in my toolbox and it is very easy to implement. Here is one of my application which is using it. And basically by just adding library to the project, you already will get information about active users, about devices, iOS versions which are used and so on. Here we can see that iOS 18 is growing rapidly fast, right? You will see users data and so on. Basic implementation is super simple. You just add library, you just add telemetry configuration. That's it. And you will already will have information like that. That's basically, I don't know, ten minute task to implement it. But you can do so much more. You can add that you can collect data from each and every screen to see which functions are used by users, what users are doing on onboarding, flow and so on. This is paid product, but what is their benefit? They are focusing on users privacy and that is privacy first application and they are kind of keeping users privacy very seriously. So you are not leaking your users data. Is that important for you or not? I don't know. You can get tools which are free like Firebase analytics. It's up to you which tool you use. But I will say one of analytics libraries are must have in your tool set. And last but not least in my list is revenue cat. Revenuecat is very important part of my app development process. Yes, you can implement in app purchases on your own and I did that more than once and for more than one project. But currently I am going with revenue cut. There are similar products like revenue cut, so choose whichever you like the best. So, but I will use this one as example why you should use third party tools for that. So it helps you to get better analytics. One thing it helps you to build paywalls easy. It helps you to run experiments. Let me show you example. So let's say here is my paywall. This top of the paywall is my custom paywall. But this bottom part that is from revenue cut. How that helps. So revenue cat helping all the purchase handling and they updating all the purchase part whenever Apple release any updates and I am using custom paywall. But if you are just starting, do not bother to build custom paywalls, just use revenue cat paywalls. Let me show you how that looks like here. This is basically the same paywall what I have in my application here. The only difference is I am using here in preview settings. I will change footer condensed. So this is part that I am using in my application here. You can see this part is from revenue cut and if I click to the all plans I see view like that, you know that all is from revenue cut. And if you are if you want to build your custom paywalls like I do, you can do that. If you don't want to bother with and don't want to do that at all, you can get all this full paywall just from one line of code in your application and that's it. And you don't need to create all the screen handle in a purchases and so on. That helps you to save a lot of time, a lot of energy on testing, troubleshooting and so on. Highly recommend to use it. As you see this list is not long and you can learn all of that in a month. Add one more month and you will have app in the app store. Will you earn the first thousand from the app store in third month? Well that's tricky. With the help of AI tools, cloud AI cursor development is easier than ever, but selling apps market theme, that still is hard. You will need to learn a different set of skills to come up with good appidays and learn how to monetize them, how to get ranking them in the app store. I can help you with that as well. There are plenty of videos on this YouTube channel. Sure, subscribe if you want to see more content like that. But in October we are running cohort training to teach all of that and if you are interested to learn more there is link in this description. Okay, see you next one. Bye.