Hello. I am a student who recently released a casual rhythm RPG game on the Play Store. I started in July of last year and developed it for a year, though honestly, I spent about 4 to 5 months slacking off or playing around. I built the server as a self-hosted one, and for the essential features excluding the game itself, this course was a huge help. I told myself I would write a review once I released it, and I'm finally leaving this course evaluation! First of all, I took both Part 1 and Part 2. - For Part 1, the content is good, but I think the price is a bit high. - For Part 2, it was sufficiently helpful. While you can ask AI for help, as a first-time developer, you don't know which features are essential to develop. This course narrowed down the scope and saved me a tremendous amount of time. [ Course-related Sharing ] 1. Preparations for In-app Sales I used a combination of a virtual office / individual business license / Google Play account (individual). After registering in-app products, the Play Console checks authentication-related matters very strictly. 2. [13] User Login Authentication Pt.1 Regarding the google-signin-unity package in this lecture, when you upload the app to the console after building, you might see a warning message saying the app may crash on 16KB page size devices and needs to be fixed. I resolved this issue by following Pull Request #205 in the GitHub link provided in the course. (Download the zip file and replace the files) 3. [34] Unity In-App Purchasing SDK Installation I'm cautious because I'm not 100% sure, but after registering in-app products in the console, you only need to install "In App Purchasing." I confirmed that the subsequent settings in the lecture were not mandatory for adding payment functionality. [ Thoughts after Solo Development ] 1. Keep the development period as short as possible, and work outside while dressed properly. 2. For small-scale or solo development, a server doesn't seem to be a necessity. 3. Understand why game genres exist; if you ignore the core fun that each genre provides, the game becomes boring very quickly. 4. Set up a way to check logs. - I recommend using Firebase Crashlytics or Analytics. - You need to be able to check at least basic information—like whether people are downloading but not running the app because it won't launch, or if they are just quitting because the game isn't fun—to be able to respond appropriately. 5. If there is no revenue, solo development eventually becomes just an expensive hobby. I received a lot of help from this course. Good luck to everyone challenging themselves with solo development! Thank you for the lectures!

Overall, the content was good and very helpful. However, I found the structure a bit disappointing. The structure is complex, yet it doesn't seem to offer any clear advantages. If it's for a lecture, it should be simple; if it's for practical use, it can be complex but should be easy to work with. It feels like it took only the disadvantages from both, which is a bit of a shame.

Wow! I really enjoyed this helpful lecture! Watching the English interview video made me feel nervous for no reason, haha.

I am enjoying your content. Thank you.