4 thoughts on “Any plan to support FirebaseUI?

  1. Hey, we’ve not really looked at this before. Generally I’m not sure what benefit it would provide – With RN it makes it simple to pull in and display an image?

    Are you looking for something like the below to be possible?

    import { Image } from 'react-native-firebase';
    
    ...
    
    render() {
      return <Image ref="some/storage/ref" />
    }
  2. I am interested in FirebaseUI so that I can use Phone Auth without writing logic to detect current country code and providing a picker for it, and writing validation logic and UI for the verification code. Kindly consider this use case. (cc: @Ehesp)

Comments are closed.

4 thoughts on “Any plan to support FirebaseUI?

  1. Hey, we’ve not really looked at this before. Generally I’m not sure what benefit it would provide – With RN it makes it simple to pull in and display an image?

    Are you looking for something like the below to be possible?

    import { Image } from 'react-native-firebase';
    
    ...
    
    render() {
      return <Image ref="some/storage/ref" />
    }
  2. I am interested in FirebaseUI so that I can use Phone Auth without writing logic to detect current country code and providing a picker for it, and writing validation logic and UI for the verification code. Kindly consider this use case. (cc: @Ehesp)

Comments are closed.

3 thoughts on “Any plan to support FirebaseUI?

  1. Hey, we’ve not really looked at this before. Generally I’m not sure what benefit it would provide – With RN it makes it simple to pull in and display an image?

    Are you looking for something like the below to be possible?

    import { Image } from 'react-native-firebase';
    
    ...
    
    render() {
      return <Image ref="some/storage/ref" />
    }
  2. I am interested in FirebaseUI so that I can use Phone Auth without writing logic to detect current country code and providing a picker for it, and writing validation logic and UI for the verification code. Kindly consider this use case. (cc: @Ehesp)

Comments are closed.