Spotify-Toolkit: Python for Spotify library management — Feedback on API fallback & architecture?

[DarksAces]

🏷️ Discussion Type

Question

Body

Hi everyone! 👋

I'm working on an open-source tool called Spotify-Toolkit, a Python application designed to help users manage, clean, and organize their Spotify libraries and playlists.

As I refine the project, I’m looking for technical feedback on how to handle Spotify Web API authentication and rate limits for desktop apps.

🛠️ Tech Stack

• Language: Python
• API Wrapper: Spotipy (Spotify Web API)
• Core Focus: Playlist organization, library filtering, and batch operations.

💬 Technical Questions & Discussion:

1. Fallback API / Credentials Strategy: How do you usually approach API keys for a desktop client? Is it better to let users supply their own Client ID / Client Secret, or provide a default fallback app credentials setup? I'm worried about hitting global rate limits or quota caps if multiple users share the same dev credentials.
2. Rate Limit Handling: For tools making heavy batch calls (fetching large playlists, deleting duplicates), what backoff/retry or caching mechanisms have worked best for you?
3. General Architecture: Any code review or suggestions on how to make the repository more modular and open-source friendly?

🔗 Repository Link: https://github.com/DarksAces/Spotify-Toolkit

I’d really appreciate any insights, feedback, or suggestions from anyone who has built tools with the Spotify API or Python!

Guidelines

• I have read and understood this category's guidelines before making this post.