Android app: outdated interface about android-app HOT 15 CLOSED

Still work to do. About the compatibility with android<3.0, it seems people don't care any more, is that right ? https://framadate.org/D52nxggEifrZ14ae

from android-app.

Recompiled the app for API level 11 and it's looking far better than before.
A thing we should consider is how we handle support for Ginger Bread user who are still at around 20% (https://developer.android.com/about/dashboards/index.html). Either compile against level 11 or use JakeWharton/ActionBarSherlock (maybe also Prototik/HoloEverywhere) to make sure it looks good on every version of Android.

from android-app.

Yes yes, cc'ing me on this one. (I reported the original issue. ;)

from android-app.

Checkout my fork https://github.com/Querschlag/android-app.
I recompiled with new Holo theme (requires Android 3.0 or higher now) and also refactored the share feature to get rid of the extra step of opening a URL in an external browser and login to wallabag.
Feedback and comments would be appreciated.

from android-app.

Nice work ! Really, many thanks.
I have just one issue when I try to synchronize.
I found why : you use username in settings page as the login username. I used it in order to set the user_id in the feed URL. But I think it's not changing. It seems to be allways the same : 1.
Could you replace the line 462 in Poche.java by :

url = new URL(pocheUrl + "/?feed&type=home&user_id=1&token=" + apiToken );

Should works as well.
After that, It will be nice to make a pull request. :)

from android-app.

Thanks for the heads up!
Does wallabag support multiple users for feed export? I think the proper way to solve this would be by adding another field for user_id to the settings page. Maybe with preset value to "1".

I will continue testing and add HTTPS support for saving page links.

from android-app.

wallabag supports multi user (we don't have GUI to manage it but it supports it. ). So you can't write user_id=1 ...

from android-app.

I would really be interested in this newer version - the one from the playstore really does not integrate well with Android 4.4 - and I d really like to put cntent in my bag without my fon browser opening my wallabag page. so +1 for the changes - and @Querschlag please merge and/or provide an akp....

from android-app.

I know I'm in the 1% here, but I'm a Froyo user and I looked for something like wallabag mainly because pocket stopped supporting my device. I like that wallabag is so small, it supports older devices and doesn't waste resources on flashy graphics which aren't needed for an app that's primarily for reading text. Of course I'm not against making it nice to use on newer devices as long as this doesn't mean we throw out support for the older ones.

from android-app.

See #25 also. My opinion is to make a wallabag-legacy package, for 2.x devices and the actual package should be upgraded for 4.x styles.

from android-app.

It sounds like a very nice idea but I suspect it would split development, so the wallabag-legacy version would not be able to keep up with feature updates in the modernised version. Is it really that difficult to have a single app work across several platform versions?

from android-app.

Well, yes and no. It would be possible to support the modern UI (except for Android L stuff) and still maintain support down to Android 2.2 or even 2.1, but it makes development a lot more clunky.
Using the standard Android APIs rather than some 3rd party compatibility library like ActionBarSherlock is better, because you don't have to deal with weird side effects.
I think that it's about time to abandon those old API levels. There are other platforms like iOS that deprecate their SDKs way quicker and consumers as well as developers can handle it ;)

from android-app.

Has there been any development for an app running on 2.1? What would it take? My comment on #25 is a look at my attempt.

from android-app.

Android compatibility packages are pretty good now. It's totaly doable to write an app with material design, fragments, toolbars and stuff and backport it back to 2.2 with only the basic SDK + compatibility packages from Google. I think it's a much better idea than supporting two apps.

from android-app.

Outdated.

from android-app.