The updated Firebase platform for Android

[nesquena]

We should document the new Firebase SDK in a "Building Data driven Apps with Firebase" that mirrors the basic structure of this Parse guide:

[ruairimcguigan]

As a former user of Parse, and having looked at Firebase as an alternative, I'm happy to pick this up and begin contributing ...

[nesquena]

That'd be much appreciated! You can refer to the https://github.com/codepath/android_guides/wiki/Contributing-Guidelines for more details about the best way to create a draft.

[baiIey]

I'd like to watch this.

Structuring data with JSON is a big part of Firebase and I'm curious how
you'll approach this instruction.

On Wed, Jun 1, 2016 at 9:27 AM Nathan Esquenazi notifications@github.com
wrote:

That'd be much appreciated! You can refer to the
https://github.com/codepath/android_guides/wiki/Contributing-Guidelines
for more details about the best way to create a draft.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#176 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAq2IKhW2Cig_1MZf4dlZizCdyt9ka5iks5qHbL7gaJpZM4IqPbW
.

[rogerhu]

@inlined might be able to help provide some guidance?

Already updated GCM guide (https://github.com/codepath/android_guides/wiki/Google-Cloud-Messaging) for FCM.

See: https://github.com/inlined/mygration as well

[inlined]

I'm probably a poor choice as an author for a guide. I'm not a very good writer and I'm a bit swamped with post-I/O polish (including Mygration) and post-I/O roadmap planning. I'd be very glad to do reviews or answer questions about Parse/Firebase/etc.

With all the new features released at I/O, Firebase is now pretty large. There are a lot of good ways you could approach either feature-based tutorials or task-based tutorials. At a high level, we talk about the Firebase features that help you develop your application, grow your userbase, and earn money. You could divide these a bit further if you wanted too. The develop pillar offers you an application backend (database, auth, storage, cloud messaging, hosting, remote config) as well as QA tools (crash reporting, test lab). The grow pillar offers tools for user acquisition (dynamic links, adwords, invites) and user retention/reengagement (notifications, app indexing). Depending on how much of the Firebase feature set you wanted to cover, these hierarchies might help your users find the tutorials they're looking for.

[segunfamisa]

I think @inlined 's idea of feature-based tutorials is workable. Firebase is now large.

I'm happy to contribute and in light of that, I've documented how to use crash reporting with the new firebase, and created an issue: #179 . Hope @nesquena and team can have a look :)

Cheers.