For those on this thread asking about a mobile app, I created Skool Kompanion (iOS only for now): https://www.skool.com/community/introducing-skool-kompanion-a-mobile-app-for-skool?p=eca3fcea https://apps.apple.com/us/app/skool-kompanion/id1660303272 The application increases engagement within Skool thanks to native push notifications on your phone. It's completely free to use so I recommend taking a look!
I'm curious if anyone had a strategic through behind their decision to go with a public or private group? Please share insights into your thought process behind this. Additionally, does anyone know if this can be changed later?
I've been thinking about the same thing recently and found this thread insightful: https://www.skool.com/community/the-weird-way-i-use-skool-i-think-its-pretty-powerful It seems like the admin of this group (https://www.skool.com/synthesizers) is using his public Skool as a centralized home from where he can attempt to make sales to his members. That in itself feels like a really powerful strategy and reason for a public group. Your community can then be infinitely large as opposed to being only paying members.
Hey everyone, Introducing Skool Kompanion - A Free Mobile App for Skool I’ve made a number of tools for Skool over the past few months such as Skool Directory or the Members Export Plugin. I believe in Skool the product and ecosystem, and am excited to see it grow. As with directory, this project was inspired by seeing numerous requests about a Mobile App. In response I’ve gone ahead and created Skool Kompanion. Skool Kompanion is a simple mobile app that allows you to access Skool as you would from a browser. It also gives you access to real-time push notifications for posts and comments at the tip of your fingers. Over the course of the last couple of weeks — I have found myself more engaged with Skool due to the way notifications keep me looped in. I think this mobile app with notifications will lead to higher engagement within your groups. I encourage everyone to try it for some time, and see how much of a difference it makes. I think it will be an essential tool in order to stay engaged and connected with your groups. At this time Skool Kompanion does not support Android, and notifications do not support chat. These are things I may look at in the future depending on support and feedback. So please try it, and let me know if you have feedback.
I think a mobile app would be super nice mainly for the community portion and communication. I'd love to be able to check my messages and posts on the go to see if I can answer quick questions without having to log in on my computer. Anyone else?
I built Skool Kompanion - A Free Mobile App for Skool This thread does a good job of highlighting the main benefit of the app, which is ultimately loss of engagement from not having notifications on your phone. Skool Kompanion solves this by giving you and your users instant access to Skool. Please check out my announcement post here
@Christina Westergaard Larsen @John Robinson @Tonya R. Portis @Lisa-Maree Walker @Ashley Payonk Checkout Skool Kompanion: https://www.skool.com/community/introducing-skool-kompanion-a-mobile-app-for-skool App Store link: https://apps.apple.com/us/app/skool-kompanion/id1660303272 Although it's not an official app, it is a fully functional iOS app for Skool with push notifications that keep you connected to your groups in real-time.
Announcing https://skool.directory/ While browsing Skool and thinking about how to be a good affiliate for the platform, I found a number of threads around the discovery of groups: - https://www.skool.com/community/group-directory - https://www.skool.com/community/recommended-communities - https://www.skool.com/community/free-skool-communities I also feel like none of the Skool marketing describes how mature and well adopted the platform is. It's only through Google I can see how many groups exist the number of users, and whether they are active. As such I've built a directory for Skool: https://skool.directory/ I hope to solve a couple of problems with directory: 1. Make discovery of other communities easier 2. Bring visibility to the fact that Skool is a well adopted and popular platform I find it very interesting to see how many groups there are and how popular they are (there are some groups with thousands of users). I have plans to do more, but I would like to hear feedback and what you think. So please let me know. And of course, if you're an admin -- please feel free to submit your group!
@Sam Ovens appreciate it! @Leah Davis I used a UI library called Mantine ... easy to use, I recommend it. @Oli Reitmaier Thanks! Inspired by how active the community is here, compared to other products I've seen.
I created Skool Kompanion (iOS only for now): https://www.skool.com/community/introducing-skool-kompanion-a-mobile-app-for-skool?p=eca3fcea https://apps.apple.com/us/app/skool-kompanion/id1660303272 The application increases engagement within Skool thanks to native push notifications on your phone. It's completely free to use so I recommend taking a look!
Affiliate signup on Skool Community The Skool Affiliate program is one of the best. I’ve built a number of tools in order to be a better affiliate of Skool and to help continue to grow this amazing community. I noticed recently that when creating a group from here, Sam always gets the affiliate credit. I think this is slightly unfair to the affiliates of Skool who are getting users to signup. Skool Community is one of the best entry points for users to see the value of Skool as a whole, and as such I send a lot of traffic to this group. I believe this group should honor pre-existing affiliate codes for users who ultimately choose to signup from here. I don’t think it’s fair to punish affiliates who want to show their potential signups this group. Does anyone else agree? Affiliates, please let me know what you think.
I built a site called Skool Directory (https://skool.directory/) for this exact reason. To help make free or popular Skools more easily discoverable. If you have a group, please submit it to get it listed.
@Emiel Kant you're correct about the higher engagement. Which is why I created Skool Kompanion (iOS only for now): https://www.skool.com/community/introducing-skool-kompanion-a-mobile-app-for-skool?p=eca3fcea Skool Kompanion gives you access to real-time push notifications for posts and comments at the tip of your fingers which leads to more engagement overall for users. It's completely free, so feel free to give it a try!
Hey all. I've started using Skool as a front-end marketing group instead of a back-end product group. Is anyone else doing this? Attached is the model I'm using. The key differences to the model most in here use: - No ads - No direct outreach - No sales tactics - No content treadmill - Focus on audience building (specifically YouTube) - Focus on community - Using Skool as a marketing community, not product community I ran the new model past Sam and he said he liked it! I also asked for permission to post this here and he said yes. I think this new model is a game-changer for getting to $100k/m profit. I know it's quite difficult to get the full picture from the image, so if you need more info then just comment "Loom" and I'll send you a Loom fully explaining the model. Hope it helps.
As I was exploring Skool, I saw there was no easy way to export your members from Skool itself. As such, I built a simple Chrome Plugin that allows for this: https://chrome.google.com/webstore/detail/skool-members-list/ccmocglnlagoepangcfikcnbkcpjcfej?hl=en After installing, you can export the following fields: - First/last name - Invite email (if you're an admin) - Profile URL - Bio, location, MBTI - Survey Questions / Answers Also, I updated Skool Directory to include tags, so you can now see all free communites for example: https://skool.directory/public Hopefully you find this helpful, feel free to try it out.
It would be nice to see how active the community is before asking to join or just a little bit more information such as the number of posts (as mentioned, would be nice to see how active the community is), who created it, and when the community was created. On the affiliate website https://skool.directory/public, you can actually see the number of posts that the community has but the community site in Skool does not contain much information if you are not a member.
@Byonghun Kwak You definitely see the vision of why I built Skool Directory. That was my first thought here on the Community Group. "So many admins with so many groups -- but I have no way to see their communities"
@Julia Weber Yah that is great. I think this doesn't even need user interface. Maybe you could just download a JSON file from Skool that has all the strings and you can overwrite them and upload as needed / desired.
Even though most people naturally speak English or at least understand it sufficiently, it would be a sign of inclusion if the few English-language terms (frontend) could be translated into the respective local language - here I'm only talking about what happens in the frontend. In the backend, most users should be able to cope well with English, but if my customers are e.g. German craftsmen, some unfortunately find it overwhelming to be confronted with the English language in the frontend. To avoid having to translate countless languages (in my case, of course, I vote for German), it would be advantageous to let the group owner do the translation himself in the settings. This way, the translation could be adjusted precisely. Additionally, it could be an enormous help to be able to export/import the translations made in the settings themselves - in the form of a language file. This way, the work would not have to be done over and over again and the translations themselves would be a community effort - similar to the contributions in Wikipedia. One could also reward such translation contributions with receiving a gem or similar. The Skool developers would then practically "only" have to implement the translation option for the individual terms and phrases in the settings and, if possible, create the option to export/import the language file. If there was an export/import function for the language file, the selection of categories (user feedback, bug reports, feature requests) could be supplemented by the category "language files" to make the own translation available to the community in a central place.