Hi Will, thanks for all your work on this library, including thorough documentation and explanations! Will you still be contributing to it after all the Unity pricing madness?
Hmm, this could probably be a whole video, lol. I just rewrote the most recent Unity apps I have been working on entirely in SvelteKit w/Capacitor. TBH the builds are much, much smaller, the dev experience is much better (esp the edit/compile/debug cycle). And the UI is better in just about every possible way. You can check out the SvelteKit builds if you are curious (the iOS builds are SK, the current Android posted is Unity). dayboard.io/ So, at this point I think anything desktop/mobile/web that's a non-game app is likely going to be SK going forward for me. Which means the one place I'd be using C# would be with Godot for a game app, but I'm still ramping on that right now. Took about a week of crashing tutorials to get over the "but everything is moved" and now I have to say I prefer Godot over Unity - so, so much faster and lighter. The C# client for Supabase is much, much richer than the existing GDScript client, and so I may go ahead and take a stab at making a template for the C# client w/Godot esp to illustrate how to deal w/the install & async/await integration. But, I don't have an active project driving this other than irritation with Unity, lol. Yeah, I should probably make a video about this. :)
@@ChangeNode Sounds like there's enough there for a video, for sure! Plus, there has been some movement on the Unity pricing too. I've also seen a few instances of people jumping ship to Godot and having a rough time of it. For the apps like Dayboard and similar I should think you'll have an easier time of it with the like of SK or Flutter. I have some 3D elements in the game I'm making, so I'm actually transitioning the MVP from Flutter to Unity. I checked out the code for supabase-csharp and gotrue-csharp, as I am interested to see how token refresh is handled. It looks like its triggered by an interval timer. I guess that means that if all the timer ticks fail, the user is logged out? I am trying to decide between implementing my own backend which talks to Firebase (and in the process having to write my own token fetching/refreshing mechanism), or whether to use one of the packages above. Advantage of the former is more security (public Supabase URL isn't exposed), but at a higher cost (in terms of dev effort + hosting)!
tl;dr no Godot template yet, maybe a couple of weeks as I ramp on Godot but if someone else want to take a stab at it rock on. Longer version: Right now it looks like there is a GDScript Supabase client already, but it's not as full-featured as the C# client. Right now the C# client would only work on desktop w/Godot 4.x. So, right now it's mobile w/Supabase on Godot 4 via the GDScript version, or desktop only C# Godot 4, or mobile+desktop Godot 3 w/the Mono version. FWIW, I'm ramping on Godot right now myself, so far it's been very interesting. Pleasantly surprised to figure a few things out (e.g. flipping on auto-switch to remote in Godot gives it a very Unity-esque play mode, except it's better in almost every way). Bunch of other stuff that's much nicer/faster. Might do an intermediate video on my initial findings in a few weeks.
By default I include a Supabase settings that point to a local instance, but you can right click in your assets folder and at the top you should see an option to create a new Supabase settings. It's just using scriptable objects to make things easier. You can of course just tweak the code to do whatever you want.
