Hello Stephen. In the pro course, I only see videos until the Matching section. I would also like to see videos about messaging and blocking. Will these videos be uploaded soon or not?
again as usual mostly only Views are covered - for me personally more interesting are - architecture of complete app and all the business logics and networking
I'm interested in taking your Tinder Swift UI Pro course. However, it says "coming soon." Do you have an estimated date for when it will be available? Also I noticed it does'nt include in-app purchases for subscriptions,or how to delete user acount, is this something you can teach to your students?
I enjoyed the lesson really, however when follow along the userinfo doesn’t show on the card view although I have made sure I have the exact same typing code.
I absolutely love the video content you shared; it's truly fantastic and perfectly meets my learning needs. I hope it will be friendly for someone like me who has no coding background.
This is a good tutorial but I see a few problems: 1) in a real app you will have thousands/millions of profiles, so you do a load of all users at once,, affecting performance. I came to this video to find a lazy load way of doing this….like having 5 profiles in memory like a stack and append and remove as necessary 2) fetching from a storagfe bucket is not shown, focusing more in architecture and I willl become a subscriber and pay for your courses PS: you also mentioned it’s a big debate if having view model is necessary or not. In my opinion is necessary so most of the code runs in the background and not in the main thread, so they UI is smooth like butter. do you know why people say we need to put all code in the main thread? just want to learn
ok new thing again, ready to learn. I hope there are more tutorials like this but with rest API integration, for example authentication which has a bearer token and how to handle it
Great video, easy to follow. Found an issue, with XCode 15.2 at time 2:09:25 the following line was added if topCard == model { ... } , however, it produces an error: Operator function '==' requires that 'CardModel' conform to 'Equatable'
