Glad to hear it!

No doubt. I'm working on upgrading RN currently and it's still quite painful.

I don’t know, I’ve never built an IOT based app. I’d used whichever technology is easiest to build and maintain the app.

I have more than 20 years experience in dev and never had issues finding a job until last year. Could it be that it is just the market so low atm?

Cool, what’s the app?

I suspect the reason there are a lot of beginner courses is because beginners all have similar problems but advanced people all have different problems. Which makes it difficult to build an advanced course that is worth your time because there will only be a small amount of people interested in buying it

@@yim Yes true. 😄 Let me revise my plan

Yes, exactly

Now ya talking

The backend is typically storing some type of data in a database, so the APIs you build will typically be pulling data from the db to send to the app or handling a request from the app to update the db. My advice would be to keep it as simple as possible and get the app into the app store/play store. When you apply for jobs having an app that someone can download is going to be a major benefit.

@@yim Thanks Jimmy I appreciate the feedback. I hadn't considered that. That actually makes a lot of sense. There have been times in the past where I would work on a project and end up quitting it because I was over engineering what I was making. Already happened a couple of times. Thanks, I am going to take your advice and keep it simple.

Yeah agreed. Launching an app is frightening the first time, but after a few launches it becomes much easier.

I’d go straight to RN. Check out expo.dev, it’s the easiest way to get started

I used Tailwind CSS on RN project and it wasn't too bad

I’m still using restyle

I have some thoughts on this, I'll make a short video later today on it.

@@yim Sweet thanks! I'll subscribe to stay in the loop

Either swift or react native could be a good option. If I was going for a job/career I’d lean more towards swift. If I was trying to make a small app to make money I’d go for swift if I knew nothing and react native if I already knew JavaScript

Thanks, Jimmy. I know Swift and JavaScript equally (un)well so I think I'll keep on trucking with Swift until I have a need for worrying about Android. There's less moving parts that way.

React Native should work well for a trivia app

@@yim Thanks for your reply Really appreciated 🙌

Seems like there are opportunities in either framework.

Do a video on an app or just a link to the app so you can download it?

Expo is a great way to build apps, especially if you are new to mobile development because you don't have to deal with all the native build stuff.

@@yim​How difficult is it to break out of expo when the time comes? I avoided it because it felt like I'd have to go through a lot of trouble to convert it back into a regular react native app.

I still love developing. If I had enough money to never work again I would still be making apps. I feel lucky because I got into development for the money but it turned out to be something I truly enjoy doing.

@@yim I feel like what you talked about creating apps without focusing on making things great might work well if you are working as a freelancer or in a startup. When you are developing apps that have long term goals, with a lot of funding you need to put a lot of thought into the foundation of the application. I have as a goal for every project I work on to make at least some aspects of it great and preferably those aspects should be ones that are reusable in many future projects.

Yeah, I see what you are saying. What aspects of the project do you want to be great and how do you define great in those aspects?

​ @yim It depends slightly on what type of app it is but some of the core ones that can make or break a project long term are imo these ones: Project structure. I am a big fan of domain/feature driven design and not using resource driven design for quite a lot of things such as screens, feature specific hooks, navigation, and feature specific components. Theming. Projects that doesn't follow a design system and instead use arbitrary values for styling tend to grow chaotic quite quickly. Wrapping dependencies. I really like the concept of trying to not use 3rd party dependencies dependencies directly within the codebase and to quite often write our own wrappers for them so that all imports come from our lib folder where our animated related functionality is imported from our @lib/animations package. What we define as great is obviously a moving target but I like to think of our implementations on an 1 to 3 scale where 1 is it works but it's not elegant and it's not easily maintainable. 2 is it works and some aspects are either quite elegant or some aspects of it make it quite easily maintainable. 3 is that it's both elegant and easily maintainable. One thing that could be the difference between a 1 or 3 for example could be something like an analytics/tracking package where 1 is just importing one dependency directly, not properly typed but it pretty much works as we want it to. A 3 for a similar package could be setting up a well typed strategy pattern where you provide a createEventTracker function where it has some default tracking provider that will be used if you don't specify anything and then you can also specify if additional ones should be used for this event tracker and it gives you a useTrackEvent hook where you can also specify if you only wanna use 1 or multiple of these tracking providers and it returns a trackEvent function which you then use to track the event.

Best way to get a job is build a real app and put it in the App Store

thanks, got it link to any roadmap if you want to share, please@@yim And I will surely purchase play store developer subscription and upload it in play store this very year. A real app 🚀🚀🔥🔥

If you only knew how “dirty” my architecture is 😂

@@yim 😅 as expert I would like to see how do you structure your folder

@@MrAvelino2010 check my other videos, I have a video where I show the folder structure of a complex app and discuss what I would do differently