migrating to?
# flutter
b
migrating to?
k
migrating to?
it definitely isn't soft migration, there is literally no documentation or anything of sort to how can u migrate from firebase to supase. for previous versions who were logged in with firebase, we showed them a migration screen where we sent them a magic link to their email.
also, had to manually migrate all data.. auth, firestore, cloud storage and tons of stuff.
b
you couldve made a script that migrates it
k
and most importantly was the fcm, i had to do my custom thingy using http extension in postgres to send an fcm whenever a database row inserted..
I did 🙂
b
functions should be out soon in Supabase
k
i have a js file, with all methods, i just have to run them one by one so firebase doesn't charge me.
I got fcm works before even supabase think of function hooks, 😄
b
coo
are you happy with the migration?
i am so far, definitely, i like the flexibility of relational db. although not so much on the auth part. it has to be natively supported.
b
so am I :/
k
I had a meeting with @User about it awhile ago, but i dont think it will come anytime soon.
I think, the mentality of supabase team has to change towards 50% web, 50% mobile.. it can't be 90% web 😄
b
well...
not really
mobile is complicated
web is just js
k
its not really complicated. let us give u the tokens for the providers. here, that's it. done 😅
I proposed an idea as well to how can we do it on mobile.
b
web is like 75% of the worldwide development (statistics by me)
the rest is most part backend
and then mobile
and mobile (imo) is not growing
k
Copy code
abstract class AuthProvider {
  final String? accessToken;
  final String? idToken;
  final Provider provider;

  AuthProvider(
    this.accessToken,
    this.idToken,
    this.provider,
  );
}
and to use it, super easy
Copy code
class GoogleProvider extends AuthProvider {
  final String accessToken;
  final String idToken;

  GoogleProvider({
    required this.accessToken,
    required this.idToken,
  }) : super(
          accessToken,
          idToken,
          Provider.google,
        );
}
b
it'll die the same way desktop dev died
backend work needs to be done in order to this happen
k
mobile will never die 😅 . u got google and apple. which will never kill their software. its alot of $$$$$$
b
not die, but get replaced by web-based stuff
k
yep, backend have to implement this. and i hope before the next supabase weekly
i dont think this will happen, google and apple are making their software to be troublesome for non-native apps. especially the web applications.
b
apple is for sure
google doesn't care imo
like
they provide the 'Install PWA App' in Google Chrome
k
which nobody uses because they never promote it properly.
it will die just like alot of things google killed.
b
lol yeah
k
I just hope supabase never sells to Facebook and we all be good 😅
b
lol
why
k
remember parse?
the firebase killer they call it? and it actually was.. but they bought, just to kill it.
b
no
im young
k
LOOL..
https://github.com/parse-community this now supported by the community
b
why would facebook kill it?
---
back to the topics
You can disable provider sign in
most famous apps doesn't have them
k
i still keep them on android, they work.
not on ios tho.
b
what?
k
yeap, i have google, fb and email on android
i had google, fb and apple on ios. but i disabled them all on ios and kept only magic link
b
why don't they work?
is it something with the lib?
k
route back. never worked
it bascially work. but the browser stuck on white screen with just done button. user have to kill app and restart
apple id, just says, not possible. probably cuz its not native 😅
b
hmm
tho
considering only email log in is not something bad
most apps only have them
most that I can remember
no big app has third party log ins
k
I peronally always use google to login. its easier 🙂 I dont have to bother with passwords and yes, most big apps actually provide social login. not sure which big ones u talking about 🙈
b
twitter
twitter
facebook
whatsapp
netflix
instagram provides facebook login cuz it's owned by facebook, so
these are big apps for me
the ones I use every day
github also doesn't
k
yeah, these are different. they are the giant ones that provide others with their own login 😄
these are the ones u use to login in with in other apps
s
I am facing same issue with android
@Kosh
i agree with kosh, native auth is used by all the apps i have on my phone + supabase do market it as firebase alternative, in-fact all mobile app devs kotlin, swift, flutter, react native would need native auth for better experience closely following this github issue - https://github.com/supabase/gotrue/issues/140