Apple doesn't have a good track record of turning their purchases into useful products for quite a while. Shame I enjoyed test flight.
Touch ID says Hi.
Apple doesn't have a good track record of turning their purchases into useful products for quite a while. Shame I enjoyed test flight.
Did you not know these policies when you started. And yet continued rather than going to say Android.
does anyone use the built-in git support in Xcode?
His company learned to work around the policies with Testflight. Now they need a new strategy.
Yes I do - best way to integrate revision control into an IDE. It's way better than the **** in Visual Studio or Eclipse. So what is your comparison basis that is so superior?
----------
You should never work around policies as that brings you in hot water. It always can be considered as breaking the policies.
But it is really simple - accept the policies or leave the platform. No one is forcing people to develop for platforms where they don't like the policies...
Yes I do - best way to integrate revision control into an IDE. It's way better than the **** in Visual Studio or Eclipse. So what is your comparison basis that is so superior?
But it is really simple - accept the policies or leave the platform. No one is forcing people to develop for platforms where they don't like the policies...
Tower.app. Github.app.
All through the Xcode 4.X versions it kept crashing randomly. In Xcode 5 it still doesn't properly support submodules, branches, etc
We started the day Apple launched the developer program. At that point we had 2 developers and 2 testers. There was 1 iPhone. A 100 device limit made sense then. Now that there are 10+ devices to support, 10+ developers on our team and 10+ million users who paid for our app, a 100 device/developer limit makes no sense.Did you not know these policies when you started. And yet continued rather than going to say Android.
Me too. At least a good simulator for iOS. I don't do development so I was unfamiliar with TestFlight.Bummer - I saw that pic and was hoping Apple was going to transform general aviation with user-friendly, crash-proof, pilot-less aircraft... Seriously, aviation is in the stone age. We need the "Apple" of aviation / air travel!
Oh god no... I hope this isn't true... TestFlight is the only thing that made deploying beta versions of iOS apps bearable. Now I expect them to ruin it by adding pointless restrictions.
Strange, I found especially Tower.app really annoying. And both are badly integrate able into Xcode - They stay external tools with all their disadvantages.
Apple doesn't have a good track record of turning their purchases into useful products for quite a while. Shame I enjoyed test flight.
what on earth are you talking about? havent used an iphone 5s?
what on earth are you talking about? havent used an iphone 5s?
How would going to Android help him test his iOS Apps?
His company learned to work around the policies with Testflight. Now they need a new strategy.
The answer to every criticism, constructive or not, isn't "just go to Android".![]()
But it is really simple - accept the policies or leave the platform. No one is forcing people to develop for platforms where they don't like the policies...
Your anti privacy statement is nonsense. *ASK* your users, not try to rip info from their lives you are not allowed to get...
Checkpoints are no more invasive than McDonalds keeping a count of which burgers people order, or a hotel keeping a tally of which types of rooms people book (e.g. 80% of customers want a double room), or the road authorities keeping a tally of how many cars drive down a particular road.
A checkpoint could tell a developer, for instance, how often customers go to an advanced settings screen. If a high number of customers go to that screen, you know it's a popular feature and you might want to think about making it easier to accomplish that task.
That's hardly a violation of privacy; it's the kind of data which is collected all the time in the real world. The developers can't possibly use that information to target you specifically; it guides general policy rather than tailoring your experience.
I only wish that these kinds of features could be integrated in to the native SDK; that is, provided by Apple. It's an essential part of application development and leads to better quality apps, so it's in the interests of both parties.
They are worse. They are like McD putting cams in your home or car to see what you do with the burger, or the hotel putting cams in the rooms to watch how you use the room.
And this is no info you should have without asking for it - everything else is spying on the user.
It actually is. Perhaps not in you opinion but here in Germany it is even a criminal act. You have to ask if you can get this info and have to respect a no.
I don't. Apple supported spying on users is a thing I definitely don't want to see.
Personenbezogene Daten sind Einzelangaben über persönliche oder sachliche Verhältnisse einer bestimmten oder bestimmbaren natürlichen Person (Betroffener).
Personal data means any information concerning the personal or factual circumstances of an identified or identifiable individual (the data subject).
No, just no. Not at all. A checkpoint is essentially a button which increments a counter (like McDonald's "customers served" tally). It gets triggered via an internet notification, but it is nothing like what you described. All the developer gets is a count of how many times the checkpoint was passed; no more than that.
You clearly have no experience of using checkpoints.
I am also in Germany and familiar with German law on this subject, and there is absolutely no way it is a criminal act. The Bundesdatenschutzgesetz does not regulate this type of data because it is not personal data and contains absolutely no personal data of any kind (BDSG §3.1):
If it was a true criminal offence, nobody would be able to count anything! Bored children would need to ask the drivers' permission when counting red vs blue cars!
It is spying on my behaviour on my systems and using my data-packages to transmit its results to you.
BDSG is the wrong law. The correct one is http://de.wikipedia.org/wiki/Computersabotage
A 3rd party has no right to do any unauthorised actions on my systems.
Not the counting is the problem - The way you do it is: hidden and by sabotaging the integrity of other it systems.
303a
(1) Wer rechtswidrig Daten (§ 202a Abs. 2) löscht, unterdrückt, unbrauchbar macht oder verändert, wird mit Freiheitsstrafe bis zu zwei Jahren oder mit Geldstrafe bestraft.
(2) Der Versuch ist strafbar.
303b
(1) Wer eine Datenverarbeitung, die für einen anderen von wesentlicher Bedeutung ist, dadurch erheblich stört, dass er
1. eine Tat nach § 303a Abs. 1 begeht,
2. Daten (§ 202a Abs. 2) in der Absicht, einem anderen Nachteil zuzufügen, eingibt oder übermittelt oder
3. eine Datenverarbeitungsanlage oder einen Datenträger zerstört, beschädigt, unbrauchbar macht, beseitigt oder verändert,
wird mit Freiheitsstrafe bis zu drei Jahren oder mit Geldstrafe bestraft.
(2) Handelt es sich um eine Datenverarbeitung, die für einen fremden Betrieb, ein fremdes Unternehmen oder eine Behörde von wesentlicher Bedeutung ist, ist die Strafe Freiheitsstrafe bis zu fünf Jahren oder Geldstrafe.
(3) Der Versuch ist strafbar.
Section 303a - Data tampering
(1) Whosoever unlawfully deletes, suppresses, renders unusable or alters data (section 202a (2)) shall be liable to imprisonment not exceeding two years or a fine.
(2) The attempt shall be punishable.
Section 303b - Computer sabotage
(1) Whosoever interferes with data processing operations which are of substantial importance to another by
1. committing an offence under section303a(1); or
2. entering or transmitting data (section 202a(2)) with the intention of causing damage to another; or
3. destroying, damaging, rendering unusable, removing or altering a data processing system or a data carrier,
shall be liable to imprisonment not exceeding three years or a fine.
(2) If the data processing operation is of substantial importance for another’s business, enterprise or a public authority, the penalty shall be imprisonment not exceeding five years or a fine.
(3) The attempt shall be punishable.