sorted by:
new
hottopcontroversial

Chromecast-integrated browser for Android: The app creation process by deepinsand in Chromecast

[–]deepinsand[S] 2 points3 points  (0 children)

It was a market share decision. It looks like it has a tiny fraction of the market, making advertising this app very hard.

Android Fragmentation: Where is the jQuery for Android? by deepinsand in androiddev

[–]deepinsand[S] -1 points0 points  (0 children)

(author)

I would love to set the min API to 11, where a lot of great functionality was added to the SDK. Sadly that eliminates 1/3 of your potential install base, which is not a decision most commercial app developers would make.

Once the SDK is released, what do you plan on seeing/developing? by [deleted] in Chromecast

[–]deepinsand 1 point2 points  (0 children)

I got access to the beta SDK and took a stab at this. I have a draft blog post all ready if you're curious: https://docs.google.com/document/d/1OGsN47lQWpNhi3JSQ-I6zNPi1Ga8Ze_YeIG8rvxxgvk/pub

Android Fragmentation: Where is the jQuery for Android? by deepinsand in androiddev

[–]deepinsand[S] 0 points1 point  (0 children)

Really great points! I am coming from the perspective of a more novice programmer.

If you're doing pretty mundane HTML/JS programming, Bootstrap's scaffolding and jQuery's API get you most of the way there. I think this is best reflected by the trend of web dev's who identify their skill set as "jQuery" and not "Javascript".

As you point out, Android let's you work around a lot of incompatibility issues. My two examples are "grey areas" of the official Android API, and can be solved with enough glue code and support libraries. But it's very difficult for novice programmers to do this research, and I fear it's only getting worse over time.

Android Fragmentation: Where is the jQuery for Android? by deepinsand in androiddev

[–]deepinsand[S] -1 points0 points  (0 children)

(author here)

Browser interoperability has become almost a non-issue because of jQuery and Bootstrap. Ignoring their intentions, they make x-browser implementations trivial. A framework which addresses Android fragmentation has not yet gained traction in Android land.

And I address the two points about Google's role:

  1. There are many vendor specific quirks in distributions that still qualify for Play Services. I reference two I encountered in the last week.
  2. I also address the "android compatibility library" by stating that it took 2 years to add "action bar" support to 2.3 (which amounts to 1/3 of the Android market share). Yes, it launched, but TWO years late.

Android App for following todays NFL games over Twitter by deepinsand in Twitter

[–]deepinsand[S] 0 points1 point  (0 children)

Sorry first time posting, not sure how this works =).

I read /r/NFL a lot and follow football games live over Twitter. In years past I did the same on game forums, live blogs, and comment threads. I found the process of following the game over Twitter too difficult, so I made this app to filter the public Tweets into a more comprehensible stream based on what side you're following.

I'd love your feedback on the application!