mParticle serves as critical data infrastructure for engineering and product teams across the Fortune 500. Developers use mParticle as an abstraction layer on top of hundreds of tools, and to enforce data privacy and data quality. Come help us build for the future of data connectivity!
Patching an APK like this would break parts of the app, specifically the parts that are arguably the most crucial to be followed by pinned API calls. For example, in-app purchases via Google Play that validate the app's signing would all fail. Similarly restoring any previous in app purchases would also fail. Finally, you wouldn't be able to install this APK without uninstalling the valid production APK first, again due to signature/signing mismatch.
Parse authenticates with GCM using the API key that you provide, as do all other services AFAIK. So, all developers need to do is use that same key in their new push provider, and their push tokens will work.
The tricky part is actually making sure that all of your push tokens that are in the Parse database are migrated to the push provider that you've chosen.
EDIT: I stand corrected, looks like you have the option to use their key as you said, my apologies! Should have figured the founder of OneSignal would know ;-)
The Soda Ban is NYC-only, in response to the city's childhood obesity epidemic. Albany is a long way from the NYC mayor's office, both geographically and politically ;)
Been having fun playing with Lambda to power various Amazon Echo skills[1]. Definitely easier than having to deploy with something like Elastic Beanstalk, or even App Engine.
We're also using this at mParticle Inc. to allow anybody to add themselves as an integration[2]. The point being that Lambda is a super-easy way to write _some_ server logic, even if it only serves as a proxy to something more complex.
Also, the improved 808 SoC at 20nm manufacturing process should offer better battery life over the 800 in the N5, even if they had the same battery capacity (which they don't, so it's a double-whammy there).
Though hard to say if this is true, it seemed their argument during the presentation was that the bigger sensor/pixels in both devices make up for the lack of OIS, and they specifically compared performance against the Nexus 6.
If I were your friend, I would tell you that this is still dubious owing to the fact that without it, many people might use very weak passwords that never change. You gotta weigh that and the vulnerability it presents for large-scale remote attacks/leaks, against the likelihood of these guys getting local access to your machine (i think?) for this exploit.
Worth noting that Apple releasing Apple Music on Android is the exception to the rule - what other 1st-party Apple software/apps are available on Android?
Also, Apple Music on Android isn't even released yet :-/
In Android it's all been rolled into the Intent/IPC system since day 1. Apps are composed of Activities, and Activities can defined Intent filters. Intent filters describe what the Activity can handle, including but not limited to URLs.
Through this system, any app can register for any url (IIRC you can filter by scheme, host, and/or path). When a url is invoked, the system asks the user which app should handle it if there are several that can. You can also set a default app for the given url, etc - the whole system, though very flexible, has been widely criticized as having mediocre UX (though IMO it mostly works just fine).
In Android M (unreleased), they've added a similar feature as in iOS 9 whereby you can ensure that URLs you define and own are always handled by your app. Essentially you host a json file at your domain, served over https, that specifies the SHA256 fingerprint of your app's signing cert. Your app defines the url filter similar to before and the system makes sure that you match the fingerprint.
Android being Android, you can still tweak the default handling of intents even if apps do this, but it's pretty hidden.
It's still pretty top-of-the line, I love mine. Best Android device in my opinion with the possible exception of the Moto X, which is very similar (just smaller and slower). The longer I have the N6, the more the size is an asset, rather than a liability.
It's actually pretty common in Android. Methinks you're an iOS user :)
> any app could register to listen to those addresses
This is core to the Android IPC design. Apps/Activities describe what they can handle (Intents, actions, filters), and I think it works pretty well. Android will ask you if you want the given app to be the default or not, and you can always un-set the default. Also, if you have a new app that can handle the given link, the next time you try to launch that link you'll be prompted to see if you want to use the new app, and your previous selected default will be highlighted as a reminder.
Also, I'm generally a believer that if an app is registering for an Intent action filter that it does not handle well/shouldn't handle at all, then users will give it a lot of bad review feedback, and apps will trend towards doing the right thing.
Do you expect to read all messages you get from a glance? How about emails? In fact, many messages you get won't be fully visible on the screen at one time - so what's the difference? Crucially - who is to say that text is all that can be conveyed when "glancing" at a watch? These things are not kindles.
I'll tell ya, I've owned both a square and a round Android Wear device. Forgetting the comparison to the Apple Watch, I much prefer the round Moto 360 to the square LG. Aside from the aesthetics - ironically, the circular display seems like it fits more on the screen, not less.
Luckily with Android you've got a choice, and the Android Wear team has built great APIs to handle both screen types.
mParticle serves as critical data infrastructure for engineering and product teams across the Fortune 500. Developers use mParticle as an abstraction layer on top of hundreds of tools, and to enforce data privacy and data quality. Come help us build for the future of data connectivity!
Product demo: https://demo.mparticle.com/ Github: https://github.com/mparticle
Our engineering team is growing fast! Come join us:
- Backend/Distributed Systems: https://www.mparticle.com/careers?gh_jid=3077965
- Mobile Engineering: https://www.mparticle.com/careers?gh_jid=2458665
- Fullstack: https://www.mparticle.com/careers?gh_jid=3009752
- Cloud Systems Operations: https://www.mparticle.com/careers?gh_jid=1219209
- SRE: https://www.mparticle.com/careers?gh_jid=3007392
- Engineering Manager: https://www.mparticle.com/careers?gh_jid=3076185
- Technical Writing: https://www.mparticle.com/careers?gh_jid=2986067
- DevTestOps: https://www.mparticle.com/careers?gh_jid=2591613
- Integrations Engineering: https://www.mparticle.com/careers?gh_jid=3044244
- All roles listed here: https://www.mparticle.com/careers
If you're interested please apply at the links above or shoot me a note (contact info in my profile).