@Darius Mora @Dima Krestyashyn Thanks for sharing, really interesting. However, those APIs rely on scraping Spotify’s public data, like play counts and regional top artists. Unfortunately, they don’t allow us to access user-specific data. @Darius Mora One workaround could be asking users to create a public playlist with their favorite artists and share the link with us. We can then parse the playlist to extract their top artists. Since users are already showing interest in this feature, here’s the simplest flow I can think of: 1. The user enters their Spotify email address. 2. We show a “Your list is being prepared” screen and let them know we’ll notify them once it’s ready. 3. On the backend, I add their email to the Spotify user management list. 4. Once added, we trigger a notification: “Your list is ready!” 5. The user logs in with Spotify, and voilà, their personalized poster is displayed :)

Downloaded and rated 5 stars, @Ryo M good luck, you got this!

hey @Diego Pérez Sánchez , I checked these tools in the past but never used them. They look interesting though! We’ve built 10+ products so far, and over time, we’ve developed our own reusable components. This makes it really fast for us to spin up new apps without relying on external boilerplates. Also, Cursor has been an incredible tool that helps streamline our workflow even more! Here’s my quick workflow: I’m using Swift 5 (yeah, I know—old school 😄) and a few Cocoapods like: • EasyPeasy (for layout) • RevenueCat and RevenueCatUI (for subscriptions) • Lottie (for animations) Happy to share more if you have more questions :)

@Prithiv Dev Devendran , I don't really use any template in cursor but I just added the rules below so whenever I ask Cursor to create the views, it follows the rules :) Here you go: Whenever new views are added to a UIViewController, follow this structure strictly: 1. Define all views at the top of the class using closures. Configure their properties such as font, color, image, alignment, etc. inside the closure. 2. In viewDidLoad(), call setViews() to handle layout and setup. You can also call other setup functions like setObservers() here if needed. 3. Inside the setViews() function, first add all views to the main view using view.addSubview(…) or parentView.addSubview(…). Do this before setting any constraints or adding button actions. 4. Add button targets immediately after adding views, before setting constraints. Example: nextButton.addTarget(self, action: #selector(nextButtonTapped), for: .touchUpInside) 5. Apply EasyPeasy constraints only after all views and targets are added. Use clear and readable layout for each view. This structure ensures consistent, maintainable code and avoids layout issues.