by: Brien Buckman

What is MasterCard?
“We are more than credit cards, we are payment experts. We process transactions 2x quicker than the blink of an eye.”

“We <3 Android”

MasterCard is part of Android Pay, but he can’t speak much about that.

MasterCard developer zone
You can play with all of their SDKs and each one has a Sandbox available. There is also documentation and support forums.  Go to “Services” and there are about 20 on there.

MasterPass – Digital Wallet Network
A digital Wallet Service that allows consumers pay with any payment card anywhere on any connected-device.

Simplify Commerce – Accepting Payments
Makes it easy for small businesses to accept payments.

“Low, Fixed Pricing – SDKs – Plugins

Merchant Identifier – Rich Merchant Data

“Provides rich merchant descriptions based on a merchant’s acquiring name.” This makes the credit card statement entry human readable instead of “JOE COFFE 342”, it would be “Joe’s Coffee on 2nd Street”, etc.

*NEW* – “Places” aggregate anonymous spend data to give you relevant merchant-focused information.”
“Say you are traveling to the middle of no where Utah, and you want a good restaurant. They use anonymous transaction data to see what the most popular payments are.

“Masters of Code” is their global hackathon. Running a lot of these events.  One is in NYC November 7-8 this year.  Get one quick, because it will sell out.

“Locations API” – For determining where MasterCard is accepted.

by: James Harmon (contact info in etherpad document)

Resources from Presentation: https://etherpad.mozilla.org/android-publish

JCenter is run by Bintray.  Their tagline is:

“Forget about Maven Central”

Artifactory is a good option if you want an internally hosted repository.  JCenter also can provide a private hosted repository.

If you publish to mavenCentral(), it will be available on jcenter() as well.

Sign up for a SonaType Acount (mavenCentral()) or a JCenter account. Jcenter seems to be easier and is the default these day for Android libraries, but this example is for SonaType:

• You need to select a group name like “com.handstandsam”
• Project url: http://handstandsam.com
• SCM URL: http://github.com/handstandsam/handstandpay.git if you want to give access to your code.

You’ll get an email back from SonaType approving you.

Create and Publish Key

Create PGP Key
gpg -gen-key

Find you Key ID:
gpg –list-keys
Key will look like: XXXXXX/YYYYYYYY <date>
YYYYYYYY is they key ID.

Now that you have the key, you can sign the library.

maven-push.gradle (you can include gradle files, so he separated this out)
Separate gradle file for pushing release and snapshot builds to repository.

Generate a pom.xml file using the ‘maven’ gradle plugin. This is useful for some repositories.

Check out your project’s depdencies using:

./gradlew app:dependencies

Example:

_releaseApk - ## Internal use, do not manually configure ##
+--- com.android.support:appcompat-v7:22.2.0
| \--- com.android.support:support-v4:22.2.0
| \--- com.android.support:support-annotations:22.2.0
+--- com.jakewharton:butterknife:7.0.1
+--- com.jakewharton.timber:timber:3.1.0
\--- com.arcao:slf4j-timber:2.0
+--- org.slf4j:slf4j-api:1.7.12
\--- com.jakewharton.timber:timber:3.0.1 -> 3.1.0

Plugin for deploying gradle builds to jcenter from Nodova: https://github.com/novoda/bintray-release

by: Konstantin Mandrika (@kmandrika) and Matt Willis (@mattwillis) from Twitter

Make sure you are using the NDK when you actually need it.  If you are making a Pong app or a Chess app, you probably don’t need the NDK.

By default, you will build for 7 types of processor architectures.

armeabi and x86 are generally good bases and will cover the majority of all processor types for android devices.

AAR libraries typically are compiled for all processor types, this can cause unsatisfied link errors when you pull in an AAR file from gradle and it won’t make much sense.  It can do this if you are compiling for the base types (armeabi and x86) because it will try to use a 64 bit version, or an armeabi-v7 version which will cause a processor type mismatch.

Tip for AAR files: You can split AARs into different runtime builds in order to fix this.

Developer Experience: They traced down a bug that only happened on one device and one version of Android. It was due to an error in Libc.  Yuck.  This is something you can’t control, so this illustrates one of the issues with Android fragmentation.

C++ STL (Standard Template Library)

• Small and very useful.  Less complete than java.util.*
• Most implementations are incomplete
• Tip: Take a copy of the STL, put it in your app, that will avoid issues for different implementations on different devices.

NDK Crash handling is EXTREMELY CHALLENGING
* Try out crashlytics: https://dev.twitter.com/crashlytics/android/ndk