1099. Payouts happen globally. Once you reach your first 400 hours building with A.Team, you unlock guaranteed, bi-weekly payments without the need to wait for the payment from the company you work with.
You have a point here. A lot has been done in the Android framework to enable developers to build app that will scale up and down elegantly. However, keep in mind that there is more than supporting the physical form factor to it. To build for tablets vs phone is a different product mindset, with different goals and user experience. I don't expect people to open BillGuard every day on their tablet, rather to take their time on weekends to go deeper into the more advanced tools for example. Since the app is used differently, the UX has to be thought through specifically to take advantage of the specific platform you're building for.
That's a very complex issue. In some ways, Google's recent design trends and libraries, e.g. as in Inbox, do not take good advantage of large screens on the desktop or in tablets. I suspect Google aimed for a cross-platform UX first, before really tackling the screen real estate issue.
On the other hand, a tablet layout that "flattens" a UI hierarchy by displaying a list Fragment to the side of a display/edit Fragment is pretty simple to do. Material Design works just fine for this, too.
Look - it's really what business comes down to. Most of what seems to happen organically was actually facilitated by creating and maintaining relationships. But that's not the main point I was trying to make, rather that as developers, we need to understand the mindset of the team behind it. They think of themselves as store managers and they want to bring the apps that will do well with their users above revenue. Another point to seriously consider which I didn't incorporate in this post is that both Apple and Google will push forward apps that make use of their latest APIs in a way that they approve of, to serve as examples to other developers and increase traction of the new OS features (example: material design, Wear SDK, Apple Watch, etc.)
Totally agree with that. The key with the App Store is to get a perfect storm of PR and feature to rise above the noise at least for a few hours/days. Then it's up to the product. Without this storm, even a good product (unless it has an immediately high viral coefficient) risk oblivion.
BillGuard indeed has only access to data in a read-only fashion. Yodlee does have a mix of web scrappers as well as data feeds for certain financial institutions. They power different features for banks such as bill payment and others but companies like BillGuard don't have access to these APIs.
It's not only about reduced visual clutter. It's about speed. You tend to use certain mobile apps dozens of times a day. A light, fast experience is crucial in this context
How does removing a helpful reminder allow me to work faster. IMO having this "visual clarity" on something that won't be used much other than the initial setup reduces speed. I'm not going to be adding new cards everyday. So only having the '+' causes me to pause and think, "What will this plus do again?"
I think that when you repeat that for every non core element, you end up providing a much lighter, cleaner look that allows you to focus on the core content. Check out the app now and wait a few hours for the iOS 7 version, I'd love to know if you disagree
