Monday, July 18, 2016

We Are Doing RxJava Wrong

So RxJava is all the rage of Java and Android Application development. But, what has bothered me is obviious question never gets answered by java developers.

Why Does It Make Sense To Give Away Half the Beneifts of RxJAvA By Insisting On Integrating It Into Our Mutable OOP Patterns?

You Do Realize That MVC/MVP/MVVM And All Their Hybrids Are In-Fact Mutable, Right?

Yeah! Do You Feel Stupid?

If I insttead use an OOP Compound Pattern than makes data immutable with the data control in functions, than I get both Composition-Over-Inheritance and Immutable with the full responsive app features instead of half of them with RxJAva.

For those following along, its similar to FaceBook's Flux:



except we are not using Reactive bindings for views but the Android OS framework components and when we do need the Director component we are using RxJava to provide that functionality.

NOTE FOR PURISTS: If I wanted to be pure the views would be recreated when updating, instead I use the Android Framework machinery and update views. And of course I am not using pure POJOs in the Domain but those with that are Parceable.

Okay, okay..to be fair when the NetFlix RxJava project started we were still dealing with those Android Devices with low Ram memory. Because everything is immutable it takes a little more Ram for this approach.

But, at API 18 and beyond we are no longer dealing with any Android Devices having low Ram and from api 16 to api 18 there is only one market where Android Devices with that low of Ram are still prevalent in the marketplace, China. Since most of us are not dealing with the China market it might make sense to switch now to this new way of Architecting an Android Application.

And by accident I found the hook to differentiate me from other Android Developers to obtain android app development gigs. As I can emphasize Huge gains in Android App responsiveness by architecting the android app in this way.



But, what to name it?

SoidumReactor?

SodiumFlux?

Tuesday, June 28, 2016

Sales-Leader Training

So I am rewriting a sales pitch on an engineering services product. Probably one of the hardest things for any coder to get as far as what dev processes fit in a start-up is that the code dev processes have to align and couple inputs to outputs across not only engineering but also customer feedback and leadership feedback.

I can do daily builds and weekly milestones all I want but absent feedback from the top of the start-up and feedback from customers it just becomes this traveling from point a to point b with no context whatsoever. And that daily builds and weekly milestones has to be done in a way to TRAIN the other people you interact with about providing feedback. You cannot just assume that they know what feedback means or how to even provide it a meaningful way.

I think of it as you are actually using the development process to train Leaders.

Saturday, June 18, 2016

Moneyball

Let's just say I found a way to sort of tell the story of preparing for getting android users for an android app in a very crowded situation. Its very similar to the baseball movie called moneyball. The IT shops and Design shops do not have the answer and that is why in the past 24 months they have removed highlighting their own android apps and only highlight the customer brands and not the app in all their advertising.

Part of the answer is what I have been doing all along in collecting together 50+ back ported UI libraries and coupling that with some tools to reduce boilerplate. That difference in developer workflow than allows that time savings to be leveraged into A/B testing of visual designs and app workflows which is where the real app users come from in a now crowded market as the one that has the right app workflow and visually stunning app now stands out.

I found a place that has that type of world-frame-of-reference so now its some heavy duty writing of the sales presentation to get the sale. A little different trip in that it means I might be moving to SV, but its a nice new adventure...YEAH!

Wednesday, May 11, 2016

Android First For Start-Ups

So I have been looking for some hooks to fine-tune my marketing message among start-ups for my dev services. I wanted to find some proof that iOS market share losses was not what the Apple PR line put out, ie changes in exchange rates.

I found that proof in this article. US market share for Android now at 65%, that is 20% higher than last year.yeah!

Tuesday, May 10, 2016

GWSAndroidTruth

Here is how you can help if you want the GWSAndroidTruth library out fast and tested. I want you when I  start publishing the articles on Medium to upvote me on reddit, upvote me on medium, follow me on fb, twitter, google+, my youtube channel,etc because than that helps me things like gig leads.

The medium articles will cover how you use Google Truth to write an api component, the type of things you use to customize how you test but in such a way that you write less test code. Its a feature that we just did not have with FEST or with assertj-for-android. Thus, its anew thing everyone should know about.

Thanks for any upvoting and or following of me on the social networks that you do.

Monday, May 9, 2016

Android Truth Testing LIbrary

Since I am switching to using Google's Truth Test Library looks like I will be creating an android specific set of libraries to deal with the UI widgets, etc.

Should be somewhat fun as its easier to expand than assertj for android was.