Thanks Andrew! Transparency and community involvement is our top priority here.
Also, we're doing a series of blog posts that will cover each part of the SDK stack. Lots of learnings to share from our kick ass SDK team.
Here's the first: http://blog.parse.com/learn/the-parse-sdk-whats-inside/
Re:Open Sourcing Our SDKs
by franklinho on Thursday August 13, 2015 @02:26PM
(#10056216)
YES! It's so important to be able to look under the hood with these things.
When I was working at MoPub, our open source SDK was one of our major selling points.
Re:Open Sourcing Our SDKs
by andrewljohnson on Thursday August 13, 2015 @07:20PM
(#10057787)
Correction, MixPanel and Segment SDKs are open source. I don't know why I thought otherwise:
I'd really like to see all infrastructure SDKs open sourced (obviously a tough sell, but maybe Parse paves the way). In building our core stack, we don't tolerate closed source. But we end up allowing it for things like Crashlytics, MixPanel, Segment, etc - and it's not a free lunch.