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 the difference between being "just fine" to creating great things.
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 dev, i love being able to read framework source code for better design, performance and less bugs. that is all really matters imho.
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.
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 all require special care which makes developing a high quality Android app very hard. My thoughts on the issue in detail: http://birbit.com/the-real-problem-with-android-fragmentatio...
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 a world class technology company where engineers love to work.
In addition to writing high quality software, we seek individuals who also enjoy the other aspects of building a new company: designing features, making good product decisions, programming at all levels of the stack, creative marketing and recruiting, and the wearing of many hats.
We are looking for extraordinary talented engineers who share similar values and who are looking to join our small family. Above all we look for passionate individuals who enjoy the craft and seek to live balanced and happy lives.
Responsibilities
Collaborate around the creation of new and existing features.
Craft and maintain world-class Android experiences.
Implement beautiful user interfaces.
Requirements
B.S., M.S., or Ph.D. in Computer Science or equivalent or 4+ years of professional engineering experience.
Experience engineering, releasing, and supporting Android applications.
Proficiency in Java.
Expert ability to get things done on a small team.
Ideally
Expert knowledge of Java.
Experience building consumer products.
Experience using Git for source control.