We’re looking for a great Android engineer to implement the Hone library for Android.
Hone is a fine-tuning tool for people building digital products. It consists of a cloud service, the Hone tool, and loader libraries on the client platforms. In a recent article, Wired Digital called Hone “a novel sensation … apiece of a much larger movement centered onrethinking how we make software”, and talked about “thrill of using Hone” to tweak apps.www.wired.com/2015/04/tool-lets-designers-tweak-iphone-apps-without-code/
We already have a loader library on iOS/Mac, and are looking for an Android engineer to bring the Hone approach to Android.
Hone library is responsible for the following features in the Hone system:
Receiving parameter values from sources like the Hone tool, Hone cloud service, and Hone document bundled with the app
Applying the parameter values to the client app’s objects, resulting in changes in the client app look and behavior
Talking back to the Hone tool about the values that the client app uses, and providing static screenshots of the client app
We don’t want you to do a straight port from iOS to Android. We want an Android library that feels great to Android engineers, while keeping true to the Hone promise of delivering a great experience to both engineers and designers. Thus, before getting to coding, we want you to help us design the best Hone Android library architecture:
What’s the best architectural approach? Should you reimplement it from scratch on Android, or develop a common crossplatform core using tools like djinni or j2objc, and then build the Android bindings on top of that? What are the pros and cons of these approaches? (This implies that you’re able to read our existing iOS/Mac library code, written in Objective-C.)
What are the existing tools and API calls to do the kind of Android live binding and introspection that Hone needs? How backwards- and forwards-compatible are they?
This is a remote contract position. You’ll work from wherever you happen to be in the world.
