Spoiler alert for those who cannot bare reading two paragraphs: it all ends well and my new silly app ends up in iTunes! Continue reading
This post is about never-ending pursuit of STR… Steps To Reproduce.
How often do you get a bug or issue report with no useful steps to reproduce it? Often I bet. The bug would be something as vague as “something broke”. Thanks.
I don’t know about you, but I find it very annoying. This is more true on Android than on iOS.
If you’ve ever ventured outside a small project that shares code between iOS and Android you would have realized that the JNI part of the share is the most tedious and at times painful. Hand-coding JNI by hand is a real pain, a lot of things go wrong: unbalanced releases, uninitialized fields, tweaking signatures as you progress with development, etc. This takes a lot of time which we are trying to save in the first place. If these sound familiar it’s likely you are sharing, or trying to share, a real object model across platforms, not just a collection of strings…
The Play2 starter template for iOS, Android and command line is a good idea if you are hitting multiple point on this list
We are getting closer to the truth. At least my version of the truth…
Very soon we will be able to share code between iOS and Android. Without commercial libraries. With 100% of source available. With only some pain.
Yes, there will be pain, so prepare!
I’d say about 4 or 5. Your pain tolerance may be different.
In future posts I will outline a less painful way to share, but it’s a good idea to go though details of this post to see what elements are at play.