by mecredis on 12/14/16, 5:24 PM with 73 comments
by unsoundInput on 12/14/16, 6:19 PM
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.
by 120bits on 12/14/16, 8:51 PM
by tthbalazs on 12/14/16, 5:51 PM
by ohstopitu on 12/14/16, 7:18 PM
I am really happy that Kickstarter has released their android app as open source - would definitely be a great learning experience!
by dblock on 12/14/16, 6:59 PM
by melling on 12/14/16, 7:17 PM
"Swift Playgrounds for iterative development and styling. Most major screens in the app get a corresponding playground where we can see a wide variety of devices, languages, and data in real time."
https://github.com/kickstarter/ios-oss/tree/master/Kickstart...
I've recently bought into this development method too. It's not quite what Bret Victor dreamed up, but it's a big step in the right direction.
by ocdtrekkie on 12/14/16, 5:32 PM
by krschultz on 12/14/16, 8:34 PM
by rezashirazian on 12/14/16, 7:28 PM
I just wish they had upgraded to Swift 3.0
by john_gaucho on 12/14/16, 7:57 PM
Kudos to kickstarter.
by alexashka on 12/15/16, 3:22 AM
I'm getting flashbacks from my last workplace where people merged in code that didn't compile and then went 'oh really? let me fix that real quick'...
Code wouldn't compile in master but the codebase... everything had to be clever. We can't just have a model, a network request to fetch/update for it, a view controller and view cells. A few storyboards and of course no bloody tests - it's a phone app.
No, we need protocols everywhere we can fit them, third party libraries - ones that haven't been out a few years (Reactive whatever), a third party library to make a basic GET request (Alamofire looking at you), a CSS styling library, a JSON to Model library, list goes on.
What we don't need is folder structure that lets you know this is the initial VC, the two folders beneath it are the 2 possible places you can go, the sub-folders in there are the places you can go from that VC and on and on.
Let's just dump all VCs in one folder, all cells in another. Nevermind that in 90% of the cases, that one cell is only ever used in that one tableview - no need to group those together.
I don't know - maybe it's just me - I'd rather I download a zip, open the project, click that triangle and it runs - this thing makes me jump through hoops, and it still doesn't work... And nothing makes sense, unless you go learn reactive cocoa - based on the amount of files/code, a clear waste of time.
by perfmode on 12/14/16, 8:28 PM
https://github.com/kickstarter/android-oss/blob/888a37468358...
by shmerl on 12/14/16, 6:44 PM
by mwcampbell on 12/14/16, 7:11 PM
by afro88 on 12/14/16, 7:10 PM
by SimonSelg on 12/14/16, 7:04 PM
by EGreg on 12/15/16, 2:12 AM
by stirner on 12/14/16, 10:14 PM