Open sourcing our Android and iOS apps
kickstarter.engineering
Open sourcing our Android and iOS apps
1–10 of 74 posts
Re: Open sourcing our Android and iOS apps
#2This is pretty awesome. Just because an app connects to a single website/service doesn't mean there isn't a benefit to being open! It's good to be able to trust (and verify) the software running on our devices.
Re: Open sourcing our Android and iOS apps
#3I had a chance to see Brandon from Kickstarter talk about their functional approach at the Functional Swift Conference in Budapest. I highly recommend watching it!
Re: Open sourcing our Android and iOS apps
#4This is pretty awesome. Just because an app connects to a single website/service doesn't mean there isn't a benefit to being open! It's good to be able to trust (and verify) the software running on our devices.
People can also learn from, and build upon the code that they've written.
Re: Open sourcing our Android and iOS apps
#5This is pretty awesome. Just because an app connects to a single website/service doesn't mean there isn't a benefit to being open! It's good to be able to trust (and verify) the software running on our devices.
This. There is really no downside to doing this, and lots of potential upside. I honestly think most companies could do this with zero effect to their bottom line.
Re: Open sourcing our Android and iOS apps
#6This is pretty awesome. Just because an app connects to a single website/service doesn't mean there isn't a benefit to being open! It's good to be able to trust (and verify) the software running on our devices.
This. There is really no downside to doing this, and lots of potential upside. I honestly think most companies could do this with zero effect to their bottom line.
If your code is bad, then there's risk of making security vulnerabilities more visible. Not that that's a good reason to avoid open sourcing, but it's a reason.
Re: Open sourcing our Android and iOS apps
#7Earlier quoted context omitted.
This. There is really no downside to doing this, and lots of potential upside. I honestly think most companies could do this with zero effect to their bottom line.
If your code is bad, then there's risk of making security vulnerabilities more visible. Not that that's a good reason to avoid open sourcing, but it's a reason.
Which is also a good reason to open your code and let those that know better help you fix it.
Re: Open sourcing our Android and iOS apps
#8Kudos to them. Compared to the web it's rather cumbersome to poke into packaged and released mobile apps, so I really appreciate access to the source of a real world app for learning and comparison.
The Android codebase looks very modern and well structured. I think it makes great use of many of the goodies (gradle, rxjava, retrofit, dagger, android support lib, ...) and learnings (bring your own MV*; use Fragments when you need them, stick to Activities if you can) that is state of the art in Android development. I think it's a great thing to skim through if you are interested in developing for Android or to compare it to you own app.
I can only assume that the same is true for I iOS. I'll certainly check it out should I start developing for that platform.
Re: Open sourcing our Android and iOS apps
#9This is pretty awesome. Just because an app connects to a single website/service doesn't mean there isn't a benefit to being open! It's good to be able to trust (and verify) the software running on our devices.
Yeah, definitely! Another cool example is the pre-alpha for Linode's new management UI:
Re: Open sourcing our Android and iOS apps
#10Earlier quoted context omitted.
If your code is bad, then there's risk of making security vulnerabilities more visible. Not that that's a good reason to avoid open sourcing, but it's a reason.
Which is also a good reason to open your code and let those that know better help you fix it.
> Which is also a good reason to open your code and let those that know better help you fix it.
This is a fantastic mentality, but unfortunately doesn't really play out in reality.
I'm a huge Open Source fanboy, but we need to be "real". How many people are really going to read every line of every open source program? Very-few-to-none is the real answer. Massively popular software gets eyeballs, but few others do.
Most of us just use the software and trust/hope someone else reviewed it for security et al.
The problem with that is, we are all trusting/hoping someone else did a review, but that someone else is trusting/hoping someone else did a review.