yeet

6 ms·

1.
A Recipe for writing responsive REST clients on Android(birbit.com)
1 points by yeet 13y ago|0 comments
2.
Android Priority Job Queue by Path(github.com)
1 points by yeet 13y ago|0 comments
3.
by yeet 13y ago
it is not the same with providing an SDK. Well, if android was documented better, we would not need source code this much but most of the time, it requires checking the actual implementation to understand the whole picture. Probably it is t
4.
by yeet 13y ago
google had a very good reason to move services outside AOSP, to update them without relying on carriers. they could release billing API v3 w/ 90% compatibility in day 1. this is how they could workaround fragmentation. as an android de
5.
by yeet 14y ago
I've been using powwow since early development days. It is a great product, been useful to me many many times. it is good to fix your mom's computer or to help your peer programmer across the sea.
6.
by yeet 14y ago
I don't think screen size is a big problem for Android. Yes it makes good design harder but not impossible. I think the bigger problem is the inconsistent implementation of low level APIs, broken functionality on specific phones etc. They a
7.
by yeet 14y ago
Path (San Francisco) Android Engineer At Path we believe in the art of high quality software craftsmanship and design. Our culture is centered around happiness and empowering engineers to have creative freedom. We are committed to building
8.
by yeet 14y ago
i love their infographics! it is awesome to see my social graph in an infographic. i wonder what they will come up with next