Android changes

[Cliff Ingham]

All of these sounds like good things to do.  Keep in mind backwards compatibility, though.  Even though we chose not to worry about it for iOS, Android 2.2 is still making up the majority of Android devices out there. (Including mine - although I'm probably goiing to be upgrading to a Nexus 4 this summer).

On 05/29/2013 03:07 AM, Rajul Bhatnagar wrote:> Thanks for the prompt reply. I agree about having discussions close to the
> code.
> Since I wrote my proposal a lot of changes have taken place in the Android
> world for the better.
> Some of them are a nobrainer to incoperate into the app.
>
>    1. The Fused Location
> Provider<https://developer.android.com/google/play-services/location.html>which
> removes all the hassles in making location aware apps in Android.
>    2. They also open sourced
> Volley<https://developers.google.com/live/shows/474338138/>.
>    It is used in a lot of the google apps on the platform. It makes networking
>    on android easier and faster. It is also very highly customizable. I was
>    thinking of replacing the underlying HTTP Stack with
> OkHttp<http://square.github.io/okhttp/>which is built on top of the
> HTTPURLConnection and offers a lot of powerful
>    features like connection pooling and response caching.Its built by Square
>    the place where Jake Wharton(the Guy who made ActionBarScherlock) works.He
>    is also one of its contributors.There has also been a patch submitted to
>    AOSP to incoperate this into the SDK.
>    3. With the release of the new support library they have standardized 2
>    powerful android UI patterns. Navigation
> Drawer<http://developer.android.com/training/implementing-navigation/nav-drawer.html>and
>    SlidingPaneLayout<http://developer.android.com/reference/android/support/v4/widget/SlidingPaneLayout.html>.
>    Both of them fit into Georeporter very well.SlidingPaneLayout can be used
>    to show the map along with all the service request listview. Also they will
>    be releasing ActionBarCompat shortly.
>
> Please tell me what you think of these.
>
>
> On 28 May 2013 20:52, Cliff Ingham wrote:
>
>> I also think that once we decide on all the features, issues, and things
>> to implement, we will use Github's Issue tracker to record them.  Then,
>> discussion about each individual feature can take place there.
>>
>> Having the discussions as close to the code as possible is a good thing.
>>
>
>
>

[Rajul Bhatnagar]

Yes all these changes ensure Froyo and above compatibility which cover 99% of devices out there.