If you could magically add one feature what would it be?

Everyday I see Skool community owners requesting new features and functionality for the platform that would improve the experience for them and their community members. Functionality that would often make a huge difference in the impact they have and the revenue they make. Many times these are feature requests that would benefit a large group of community owners but for others they would be kind of useless. So it’s understandable why the Skool them wouldn’t implement these; They are no core features, the platform would quickly become overwhelmed with features and would lose the simplicity and ease of use that has attracted so many community owners in the first place. Shopify faced a similar challenge in 2009. They were stuck between keeping their platform simple and adding features some merchants needed to grow. So they launched the Shopify App Store, which was crucial to Shopify becoming one of the major players in e-commerce. This let merchants and developers add extra features to their stores, but only if they wanted them. It didn't change how simple the main platform was for everyone else. Even the apps that get added have to follow Shopify UI and UX guidelines and must be approved by them. After the App Store launch, Shopify's growth took off. They went from a small Canadian startup to a global e-commerce giant, now powering over a million businesses worldwide. Until this day their App Store is one of their biggest moats against other ecom platforms. It seems that Skool is kind of going this route with Plugins. The next step would be to open the Plugin store and allow developers to create third party plugins through the Skool API. Here’s how everyone wins with this: -Community owners get extra functionality that might be not a core feature of the platform or useful for everyone but a game changer for a lot of them. There would be already a plugin for language translation, other currencies, different pricing models (free trial, affiliates, etc). Or some of the functionality Sep requested here (https://www.skool.com/community/6-feature-requests-thatll-6x-group-owner-revenue)

Every day, Skool community owners request new features to improve their experience and grow their revenue. Some of these requests would benefit many owners, but others wouldn’t. It’s understandable why Skool avoids adding too many features—it could overwhelm the platform and compromise its simplicity. Shopify faced a similar challenge in 2009. They needed to balance keeping their platform simple while allowing merchants to grow. Their solution? The Shopify App Store. This allowed merchants to add features they needed without complicating the platform for everyone else. Shopify kept their core platform simple, while apps followed strict UI/UX guidelines and were approved by Shopify. The App Store launch fueled Shopify's growth, turning them into a global e-commerce giant. Now, Skool seems to be heading in the same direction with Plugins. The next step would be opening a Plugin store, allowing third-party developers to create plugins via the Skool API. Everyone wins: - Community owners get extra functionality that’s not core but critical for some (e.g., language translation, different pricing models). - Skool stays simple, as plugins must follow UI/UX guidelines and be approved by the Skool team. - The Plugin store becomes a testing ground for future core features, just like Shopify apps. Would love to hear your thoughts on this. (all credit goes to @Diego Roshardt - just simplified his post to the essence)

I would like to see a co-owner option on skool. I am technically owner with my partner @Jamie Kullman of three communities and would love to see this feature! The moderator feature is great but that is not co-owner.. 🤔 Who else would like to see this feature???

I love Skool. My clients too. The only thing we (really) miss is TRANSLATION! I believe it's time for Skool to release text customization for the main parts of the platform. This way, admins could translate their own communities however they want. An advantage of this first option would be the possibility of changing the main sections of Skool to something more similar to the community theme. For example, we could change "community" to "mastermind". Or "classroom" to "courses", "programs", "workshops" or something more suitable for each case (in our own language). If this is too complex, something that would also work is the multilingual option for users (community members) to select. Or the same for admins to choose in their own group settings. Either way, the platform would be perfect with language translation. Do we have any predictions for this update? Is this on the roadmap? Thanks in advance @Sid Sahasrabuddhe, @Sam Ovens and all the team! — Viktor P.S. For context, we have a copywriting program here in Brazil, and we only sell to Brazilians — who speak Brazilian Portuguese (PT-BR). The vast majority of them don't speak English and one of our main selling points is that they won't have to translate copywriting books on Google Translate (because everything we do inside the program is in our native language). So, it's a little strange for them to use a platform in another language. Our current "workaround" is Google Chrome's automatic translation. But it's horrible and only works in the browser.