Isn't that what these pesky "regulations" are? You know - "laws".
94 karma · joined September 9, 2010
android.permission.WRITE_EXTERNAL_STORAGE ==> needed to write images to external storage android.permission.ACCESS_NETWORK_STATE ==> pretty much anything that needs to have a working internet connection android.permission.READ_PHONE_STATE ==> link tracking android.permission.GET_TASKS ==> crash reporting android.permission.READ_LOGS ==> also crash reporting but probably doesn't work in 4.3 android.permission.GET_ACCOUNTS ==> Google Cloud Messaging...seriously android.permission.WAKE_LOCK ==> also GCM
etc.
And when you add ad networks it gets worse. And, they also pay more for gender, location, and age so thats why everyone wants you to sign in with Facebook, etc, because otherwise you can't pay the bills.
I don't know why this is a big deal. Isn't Google already vacuuming up this information from their Android users anyways via "Google Play Services".
First off, rent control doesn't apply to apartment building built after 1979, so, as noted below, its less relevant - especially with the new construction in SOMA.
Second, the anecdotal stories about landlords holding units off the market is just that - anecdotal stories. The owners of those buildings are Prop. 13'ed with a 30yr old assessment and are doing just fine. Opening a new unit means they can collect more rent at todays market rates. Its a silly story promoted by landlords that would like to make more money during the booms. Of course, its also those very rent control laws that protect landlords during the busts (2002, 2009, etc).
Sorry to say this, but rent will come down when companies in SF start running out of their free, investor money and have to turn a profit or sell themselves. More people will lose their jobs, won't be able to afford living in the city proper and people will move away. Thats the way it has been here for at least the last 20 years and probably longer.
By the way, also anecdotally since I can't find the reference, rents in the area have decreased by 5% on YoY basis.
Then when you get to single stepping its ridiculously slow. Anyone that has used or attempted to use the NDK debugger cannot say with a straight face that it is up to par with modern tools.
Oh...then there is the issue of ridiculously uninformative stack traces.
Its generally easier to build your code in an x-plat fashion in C++ and then work out as many bugs on iOS as you can and then - as the parent said - leave printf turds everywhere.
Stone knives and bear skins...
Whether you are looking for employment with someone else or starting your own company, having a broad set of skills is always valuable.
I'm talking about KISS the band!
You basically need to tell yourself that you made the Best F--ing Game in the World and use that to fuel you past all the disappointments in the marketing - cuz it IS hard work and there is no magic bullet.
Also, you should be using this game to build up an "installed base" for your next game. Get fans on facebook. Build up a mailing list. Have a way to message existing users. etc.
One last thing, since I'm on my soapbox, is that I think this whole $0.99/unit business model is somewhat unsustainable and really works to the advantage of the big publishers and against indies. It really is in the best interests of the publishers to keep the accepted price point at $0.99 because only they have the economies of scale and connections to move enough units to make a hit - or if it isn't a hit to just move on to the next title.
While I agree with your general feeling on tax cuts, this should be seen as a new tax that should never have been implemented in the first place.
The fact that city hall is specially treating some companies (Twitter) is even more odious and unfair to other startups in the city.
I don't think the "joke" aspect has anything to do with it. We recently had a joke app published on the app store with no problems at all. In fact the first submission of the app came after the rule clarifications they did (last Sept? Oct?). Of course the humor(?) in our app doesn't revolve around ripping people off ("Ha ha...you bought our in-app purchase. Jokes on you!").
I'm actually a little sorry I clicked the original article link. It sounds like they spent two days on something with the specific purpose of getting some publicity around a rejection. Mission accomplished, I guess.
In fact, I've found the docs for Android to be of the "broad but shallow" variety. That is they cover everything (thanks to Javadoc) but they don't necessarily provide usage guides on the various APIs.
My opinion on Android development vs. iPhone is:
a. GC is convenient
b. The developer docs on Android are not nearly as good as Apple's
c. XCode (while not perfect) is less buggy than Eclipse for basic development activities. Eclipse just gets in the way most of the time and can't keep up with my typing speed which is really frustrating.
d. I like ObjC's dynamism a lot more than Java. This is a personal preference.
e. Its nice to be able to peer into the OS source on Android as the definitive answer for API questions but I suppose if the docs were better you wouldn't need to do that.
f. The Android APIs are full of pattern inconsistencies with their implementation on the whole compared to UIKit which make them more difficult to learn.
g. UI Layout on Android is abysmal compared to using Interface Builder.
i. Again - this is more of a Java thing, but Android lacks the ability to do conditional compilation. You have to go through build system/scripting gymnastics to get what you would get from a simple #IF statement in C.
b. The author of the article is speculating when worrying about buffer overflows and javascript execution. I doubt most wispr parsers even use traditional XML parsers. Besides, its much easier to spoof an AP or execute a man-in-the-middle attack than anything else.
c. The magic whitelist as you call it, is publicly documented and is called "Captive Networks". You can read about it in the iOS documentation. But I suppose its more fun to try to bash without any knowledge.