neilkimmett

ClassPass | Android Engineers | US (NYC, SF, Missoula, Houston, Remote)

We're the world's largest app for studio fitness and wellness and we're looking for both junior and senior Android engineers to help grow our app. The app is mostly in Kotlin, makes heavy use of RxKotlin, and we also use Kotlin on the backend

Apply at https://boards.greenhouse.io/classpass/jobs/2535337

Learn more about us at https://classpass.com/about/careers

They are asking for users phone numbers: very sensitive data. Apparently that data is not being handled securely.

Massive congrats and thanks to all the CocoaPods team for this. Such an important project in the Cocoa community. New way of publishing pods looks much smoother.

Ling gave a good talk about it, you can watch it here http://www.besquare.me/session/the-future-of-digital-marketi...

In iOS7 you can granularly allow/disallow apps access to: location services, contacts, calendars, reminders, photos, bluetooth sharing, microphone, motion activity (iPhone 5S and new iPads only)

The first time an app tries to access any of the above you will be asked whether to grant it permission or not. You can then edit this preferences in Settings.app > Privacy

Totally agree with giving them the benefit of the doubt, hence https://github.com/Mashape/unirest-obj-c/pull/9

I still doubt as much thought has gone into it as a more mature library like AFNetworking (https://github.com/AFNetworking/AFNetworking) though. Even then the new NSURLSession APIs in iOS7 pretty much remove the need for a 3rd party networking lib.

Yep things like this, lack of class prefix, and using [NSDictionary dictionaryWithObjectsAndKeys:@"application/json", @"accept", nil] instead of modern literal syntax @{"accept": @"application/json"} are a bit of a red flag for me.

I love how the instructions for "how to make a chair to cross a stream" are: 1. swim across the stream 2. make a chair to cross the stream

Exactly. From the Apple Human Interface Guidelines (https://developer.apple.com/library/ios/#documentation/usere...)

"Avoid using your launch image as an opportunity to provide:

- An “app entry experience,” such as a splash screen - An About window - Branding elements, unless they are a static part of your app’s first screen

Because users are likely to switch among apps frequently, you should make every effort to cut launch time to a minimum, and you should design a launch image that downplays the experience rather than drawing attention to it.

Generally, design a launch image that is identical to the first screen of the app."

Not sure why he/she deleted their post, but for an excellent in-depth analysis of App Store pricing I thoroughly recommend Michael Jurewitz' 5 part blog post "Understanding App Store Pricing"

http://jury.me/blog/2013/3/31/understanding-app-store-pricin... http://jury.me/blog/2013/3/31/understanding-app-store-pricin... http://jury.me/blog/2013/3/31/understanding-app-store-pricin... http://jury.me/blog/2013/3/31/understanding-app-store-pricin... http://jury.me/blog/2013/4/1/understanding-app-store-pricing...

Theres a bit of Economics 101, and some very well explained real world data on app pricing. Essentially Michael's advice boils down to: try doubling your price. If you lose less than half your sales, you're now making more money than you were before.

Theres the Django tutorial but its not quite as comprehensive as Hartl's Rails Tutorial.

https://docs.djangoproject.com/en/dev/intro/tutorial01/

Obligatory link to the moronic Daily Mail article about gov.uk:

"And the award goes to boring.com! Government website beats off 100 others to be named world's best design" http://www.dailymail.co.uk/news/article-2310191/And-award-go...

If the drug makes the condition worse?

Yep, if you want to see what they have you can download it all: https://www.facebook.com/help/131112897028467/

Well that seems thoroughly unreasonable.