181–190 of 197 posts
Earlier quoted context omitted.
I notice you're syncing tasks every minute. Perhaps a short-term workaround is to sync every 2 or every 5 minutes while you wait for the quota to increase?
That can be done but it will affect user experience right ? Better will be if I stop further registrations for the app.
Earlier quoted context omitted.
You might get an SLA for money but you can't stop a product from disappearing.
But if you have a contract, you can at least expect the product to exist for the term of the contract.
Earlier quoted context omitted.
After reading through this thread it appears to me that all that is stopping you from launching is a couple of bugs related to multiple Google accounts use case. I would call that an edge case and launch the rocket. Just drop a comment about it in the FAQ. Unless, your product is strictly about multiple Google accouncts in which case you are shafted. :)
The part of the Google Drive market you can make money from with our application (it's B2B) is the Google Apps for Business accounts, that means Google Apps domains accounts (not personal ones). The majority of users logged into Google Apps Domains accounts (and we measured this) are also logged into their personal account on that same browser. This means more than 50% of our target market can't share documents throu…
I think that Google is wasting huge ammounts of goodwil through its lame operation of GAB.
One does not simply not run a customer service.
Edit: To add a bit more substance to this comment. I kinda know wahat you are going through. I took it upon myself (after numerous have failed) to push through something that looked like a pretty nasty bug in Lotus Domino 8 server and client. Basically what I found out during research is 20% of IBM 852 (its internal datatype) was simply corrupt.
And boy for the longest time nobody responded. There were IBM SWAT Team Leaders guarding the sacred Process that would insist on telling me that there is no Bugs in their platform and that it is obviously my fault. It took six months, an extremely detailed testing procedure with test cases and invoking a lot of connections to get my report infront of a person that could actually understand what is going on.
Soon after that I received a hotfix. I had to repeat the whole procedure another two times. And by the third time I could get it done in three months. I basically made the blue elephant dance just for me.
So for what its worth my advice is to invoke every and all connections within Google not to just get your issues within an internal Google issue tracker. You need to find out (from the outside) who is the guy responsible for the general area that is causing you problems, then keep in touch with this person and after some time you will get your fix(es).
If you build something on someone else's API, you can get fucked in a million ways. They might shut down the API (Google Reader), take away the functionality you relied on (Google Calendar), limit it (Twitter) or deprecate the version you're using, forcing you to do development work to keep working at the worst possible time for you (IOS). They might also decide that your product is very good and build a version of i…
Can someone take the time to explain to me what this means for someone who has an interest in developing Android apps that may make use of Google APIs? I don't know how quotas work and why it sounds like you could request an increase when you hit a limit, wouldn't they want you to move to a paid tier? Does this mean that as soon as your app becomes popular, you are doomed to fail? I've looked briefly at a few Google…
Some services have prices over the courtesy limit (Translation) while others just have a max. What happens for like the Books API when you get above 10k/req/day?
Earlier quoted context omitted.
> Google is phenomenal on their technical merit They turn into Microsoft where brilliant engineers are bogged down by corrupt management :)
Funny that all the Google product managers I know personally are ex-Microsoft guys.
This issue almost took more than a year to get fixed - I had to drop a project midway and start with other technologies from the scratch to build the same thing.
The developer experience could have been better.
If you build something on someone else's API, you can get fucked in a million ways. They might shut down the API (Google Reader), take away the functionality you relied on (Google Calendar), limit it (Twitter) or deprecate the version you're using, forcing you to do development work to keep working at the worst possible time for you (IOS). They might also decide that your product is very good and build a version of i…
Don't forget "They might break the API without warning. Every two to three months. (Facebook)." Your argument is exactly why I don't use Google AppEngine. I know there are open-source stacks now that you can use if you want to take your AppEngine code in-house, but trying to build up an AppEngine infrastructure at probably the worst possible time ("we're getting billed @ $10k/month, but only making $8k! getting more…