Sharing your custom app

[3raxton]

Hey there,

I've seen your custom app for Spicetify and understand the struggle of getting them out to users. I've recently created a community based repo for developers of customs apps to share their apps.

If you're interested in creating a pull request to share your custom app with others who are searching for different custom apps for Spicetify, feel free!

Please don't feel required to create a pull request. However, I figured I'd share the repo with you since you've created a custom app, and you may be interested in getting it out to users.

https://github.com/3raxton/spicetify-customapps

Cheers!

[theRealPadster]

Hey, thank you for your interest! I do like the idea of having a central place where users can find Spicetify extensions, since I looked for one myself when I developed this one, and didn't find one.

However, I'm not really a fan of the "Donate" paragraph, as it gives the impression that you are the main contributor for the apps listed in the repo, and directs any funds towards yourself.

This is likely not your intent, and I would suggest updating the paragraph to clarify your role, and to include a list of the apps and links to their repos/websites, for proper attribution.

I know that it is a very early stage project, and no other apps have been added yet, so there's not much to add or link there, but I could try writing something up quickly (which you are free to modify and contribute to) in my pull request, if you'd be open to this idea.

[3raxton]

I totally understand that, and I'll remove it. It's a bit embarrassing because I make my repos by using template READMEs and repo layouts then replacing the common words within the README. Definitely not an intentional thing; my bad! 😅

Good idea for the attribution! Would you elaborate a bit more on that so I can understand what you're envisioning?

Thanks again for making me aware of my mistakes! Changing the donate section (again, sorry) now!

[theRealPadster]

Haha all good, thank you 🙂

I would add a section near the top of the readme somewhere that has something like a bulleted list of the apps included, and a link to their repo+author.

e.g.

Attribution (or "Included Apps/Extensions" or something)

This repository is a centralized collection of community-made custom apps/extensions for Spicetify. Thanks to these awesome people who make Spotify better for all of us!

• spicetify-hide-podcasts by theRealPadster
• custom-app-2 by someguy83
• some other app and yet another app by SomeoneElse

---

The links would go to the relevant pages, of course, and that's just a rough idea not final copy or anything. Probably should also edit the Contributing section to include a bit on adding your app to the list.

[3raxton]

I think it's a solid idea, but I’m afraid of how long the README could become if many apps are added to the repo. This could be solved with a simple details tag or a second markdown file with a mention of it in the README. I’ve used a details tag before in a previous README, and it’s fairly overwhelming, so I’m hesitant.

Any thoughts on a second file for attributions with a mention in the README to prevent overwhelming readers? On Jan 1, 2021, 22:28 -0600, Isaac notifications@github.com, wrote:

Haha all good, thank you 🙂 I would add a section near the top of the readme somewhere that has something like a bulleted list of the apps included, and a link to their repo+author. e.g. Attribution This repository is a centralized collection of community-made custom apps/extensions for Spicetify. Thanks to these awesome people who make Spotify better for all of us!

• spicetify-hide-podcasts by theRealPadster • custom-app-2 by someguy83 • some other app and yet another app by SomeoneElse

The links would go to the relevant pages, of course, and that's just a rough idea not final copy or anything. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[theRealPadster]

Ah, fair point. A separate attribution file would also work. I think each extension will probably also have its own readme in its folder regardless. What is a details tag?

[3raxton]

I agree. I think something like an attribution.md file would be the way to go with a mention of it in the README.

As for the details tag, it’s the

HTML tag that allows for rolling down/up a section in HTML.

I’ll set up the attribution file soon unless you’d like to initiate it with a PR. On Jan 2, 2021, 21:06 -0600, Isaac notifications@github.com, wrote:

Ah, fair point. A separate attribution file would also work. I think each extension will probably also have its own readme in its folder regardless. What is a details tag? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[theRealPadster]

Ah, I see. Yeah the details tag would make the markdown kinda messy. A mention in the readme with a link to the attribution.md would be fine. You can set it up if you'd like. It'll probably be a few days before I get around to my PR.

[3raxton]

This week is going to be fairly packed for me but I’ll set it up. Feel free to watch so you can see when I add it.

Thanks again