Enjin was launched at a time when "website builders" were the only way to really manage your team, and that's still what it is today. A few problems with this approach:
1. I might just want to have a team calendar, and I don't really want to create a website to use a calendar any more than I want to create a website to use Google Calendar. You can create a team and access all the tools on Guilded in 10 seconds.
2. Enjin has poor mobile support as a result of this philosophy, because user-created websites on a desktop don't tend to work as well on mobile. They certainly won't work well as an app.
3. Because all of the features that Guilded teams use are integrated in a first-class way, we can do really cool stuff with your network connections, like share your updates to your Discord server, notify your team when you go live on Twitch, etc. Many of Enjin's are third-party html/js/css, so they don't have that level of control.
These problems are ones that I wanted to solve, and they were a large part of the motivation to build this.
1. I might just want to have a team calendar, and I don't really want to create a website to use a calendar any more than I want to create a website to use Google Calendar. You can create a team and access all the tools on Guilded in 10 seconds.
2. Enjin has poor mobile support as a result of this philosophy, because user-created websites on a desktop don't tend to work as well on mobile. They certainly won't work well as an app.
3. Because all of the features that Guilded teams use are integrated in a first-class way, we can do really cool stuff with your network connections, like share your updates to your Discord server, notify your team when you go live on Twitch, etc. Many of Enjin's are third-party html/js/css, so they don't have that level of control.
These problems are ones that I wanted to solve, and they were a large part of the motivation to build this.