☂️ FlutterFire Pigeon Migrations

Open
#17,667 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Domain
mobile-dev

Research direction

Review the unchecked package entries: Authentication, Cloud Firestore, Cloud Messaging, Core, and Cloud Storage. Compare their current Android, iOS, and macOS implementations with the stated Kotlin, Swift, and Pigeon migration goals. Done means the remaining packages are migrated and their refactors are complete.

Written by the indexing model from the issue text.

Description

Needs Attention platform: all type: enhancement umbrella

What is Happening

1 - Migrate Java to Kotlin Android side.
2 - Migrate Objective-C to Swift iOS and macOS side.
3 - Using Pigeon instead of Method Channels

Packages

Progress:

  • Analytics
  • App-Check
  • Authentication (Pigeons done, needs Refactor)
  • Cloud Firestore (Pigeons done, needs Refactor)
  • Cloud Functions
  • Cloud Messaging
  • Cloud Storage (Pigeons done, needs Refactor) In Review
  • Core (Pigeons done, needs Refactor)
  • Crashlytics
  • In-App Messaging
  • Installations
  • Performance Monitoring
  • Realtime Database
  • Remote-Config
Dominant language
Dart
Stars
9.3k
Forks
4.1k
Avg merge
2d 10h
Merged PRs (30d)
78

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/flutterfire

All issues in firebase/flutterfire

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.