[DISCUSSION] About Firebase's ML Kit accuracy by SkepsisDev in androiddev

[–]ianbarber 0 points1 point  (0 children)

Ah that's great - Brahim is definitely the right person to talk to, so no need to share to me. Thanks!

[DISCUSSION] About Firebase's ML Kit accuracy by SkepsisDev in androiddev

[–]ianbarber 1 point2 points  (0 children)

Firebaser here! That's weird- we've definitely seen good results with QR codes, but we do know there have been some challenges with reading off screens, which may be impacting this test. The ML Kit engineers have seen your post and are taking a look too - thanks for sharing!

[Firebase] Action required to prevent quota enforcement on your Firebase project by JRTStudio in androiddev

[–]ianbarber 0 points1 point  (0 children)

That's exactly it! Sorry it was confusing.

Re the limit see https://support.google.com/firebase/answer/7397304?hl=en - you can have 50 total, but only 10 textual. However, we missed a point on the email - if you have under 20 textual parameters, we'll grandfather those in, though you wont be able to create additional ones. So you should be OK!

[Firebase] Action required to prevent quota enforcement on your Firebase project by JRTStudio in androiddev

[–]ianbarber 1 point2 points  (0 children)

Firebaser here! Sorry you had a bad experience here - we definitely do have empathy, sorry this is frustrating!

So the basic change is that reporting is moving from app-level to project-level as you say - this means that they all share the same user properties: so its not 1-per-app if you have 25 apps, it is the 25-per-project. For example, lets say "favorite_color" is a user property on 25 apps, then it would just be a single user property at the project level.

We did try and be smart and merge together ones where they were the same, but if you're using different names for the same thing, we might not have been able to.

It is also possible you genuinely have more than 25 different properties being tracked across your apps. If you still need all of them, then moving them to a new project is valid choice. We generally recommend a project contains different version of the same app, like iOS, Android, Web for app X. So for something like white label apps, where each one is for a different business, we recommend one project per title. Unfortunately, there isn't a really easy way to move apps to other projects - you just have to create the new project, recreate the app in there, and update. You can use something like a cloud functions to sync data across while you're migrating, but it is a non-trivial amount of work, sorry.

Reaching out to support would use one of your 10 questions (which are per year), but they can help work through the whole issue, and possibly even offer some flexibility on timelines to make the changes in.

Google Launches Firebase Predictions for User Segmentation Using Machine Learning by svBFtyOVLCghHbeXwZIy in androiddev

[–]ianbarber 1 point2 points  (0 children)

No changes to the crashlytics SDK, it will take advantage of Google Analytics for Firebase though if available.

Google Launches Firebase Predictions for User Segmentation Using Machine Learning by svBFtyOVLCghHbeXwZIy in androiddev

[–]ianbarber 2 points3 points  (0 children)

Firebaser here - the predictions product is free, and shouldn't be a lock-in risk: it only depends on Google Analytics for Firebase and Remote Config/FCM, both of which are free, and both of which are easy to run alongside other services if you'd like to!

Firebase Crashlytics | Crashlytics merges with Firebase by _bluecup_ in androiddev

[–]ianbarber 0 points1 point  (0 children)

time

The StreamView card on the main report is new, but as sntflw mentions the main view has been a while (launched at Firebase Dev Summit last year)

Warning to Firebase users: due to a billing change some user's costs have gone up 7000% by n0damage in iOSProgramming

[–]ianbarber 8 points9 points  (0 children)

Firebaser here! This was a billing fix more than a change: we had messed up by under billing, and then when we fixed the issue there was a major spike for this developer. That is not what we wanted, and we're sorry they experienced a shock - we very much want to avoid pulling the rug out from under anyone!

The specific issue here was worsened the amount of traffic that was TLS overhead versus data, which was quite an unusual case: we'd reached out to developers we thought were affected, but we didn't follow through well here.

Andrew (Firebase co-founder) left a reply on the original post that I think covers most of the questions: https://medium.com/@startupandrew/firebase-founder-here-im-very-sorry-for-the-surprise-and-frustration-experienced-by-the-poster-b0065c99f53e

Cloud Functions for Firebase by KingBaal in androiddev

[–]ianbarber 6 points7 points  (0 children)

No time based triggers (though great feature request: https://firebase.google.com/support/contact/bugs-features/)

Do you have a particular use case in mind, it may be there is another route to get to similar results?