iPhone App In App Store Limbo Open Sourced
recoiledsnake writes "The author of iPhone prototyping tool Briefs has decided to open source it after the App store submission has been in limbo for over three months. The app had got into trouble for what Apple believes is being able to run interpreted code, though the author denies it, saying all the compiling happens on the Mac. While Rob stays civil, his co-worker blasts Apple for not even rejecting the app. Three months is nothing compared to Google Voice for the iPhone though, which is still being studied further by Apple after more than a year."
Can someone explain to me why Apple behaves this way? I fail to understand. What even bugles my mind is the fact that Apple as a company is [still] a darling in many people's hearts. No bad publicity sticks.
I for one, will not touch an iPhone even with a 10 foot pole for my HTC Incredible does all that want it to and even more. The trouble is Oracle that is threatening to cut off Android's air supply with patent suits against Google.
One would think he could easily cross to the dark side, and release his app in the Rock store, or the Cydia store.
In fact, I would be surprised if someone doesn't take the code, compile the app, and release it as a .deb anyways.
But using the Cydia store features the developer could still make quite a bit of money.
Sure, it limits your app to jailbroken devices, but that is a very large number of devices compared to zero as the current situation goes.
I'm sure he has his reasons and all, I am just curious what they might be.
I don't know if this technically qualifies as open source, and it's not Free Software, because of this line in the license:
"The Software and/or source code cannot be copied in whole and
sold without meaningful modification for a profit. "
You're a good example of why some animals eat their young.
His product is one that creates wireframe prototypes of iPhone apps and allows you to run them on the iPhone. Presumably (from his experience, and others he's shown it to) this allows you to make better apps faster.
He shouldn't be surprised, he is running into essentially the same trap that was built for Adobe when they tried to create a compiler for Flash that translates onto the iPhone. Apple has said they want to be completely in control of the development environment, and anything that threatens to take away that control will not be allowed. They've written this into the license, and explained it several times. There is no reason for him to be upset over something he should have realized.
Now, if only someone would write a decent GUI builder for Android, I would be happy.
Qxe4
An offtopic thought: given the recent (re?)surge of seemingly organized trolls here, mod points allocated by the automated system are going to waste, both from the karma-whoring trolls to mod up their own posts and from the people in the audience/freakshow modding them down. I have come across recent discussions in the usual places regarding playing the Slashdot moderation system, so I think the question must be asked: how many points wasted would be needed to destabilize the system by impoverishing it? If the number of posts and moderations increase and remain stable over a period of time, malicious or not, will the system compensate?
Emotions! In your brain!
In his blog post about it he has this "aw shucks, time to go write some apps Apple will approve" attitude.
/yeah, this post went in a completely different direction from where it started
It strikes me as the psycho ex gf/bf who cant accept Apple broke up with them and refuses to mail order a new Android companion (or at least get a RIM job)
meep
Three months is nothing compared to QA times for the T-Mobile Sidekick. Small teams can't afford to wait a year from submission to first profits, especially when you're writing software on spec (not sure if it'll even be allowed onto the platform). When you outsource your QA and pay them per bug they find, you're going to get a lot of non-bugs and a lot of repeats, and the developer is going to get pissed. I know my team and I did.
Welcome to the mobile software industry, where your target platform doesn't care about you because there are 600,000 other developers who'll bend over and take it if you won't.
No, he's emotional. GET IT RIGHT!
And so does Sony AND Nintendo. I am of course talking about game consoles. Closed platforms where the owner of the platform (not you dear consumer sheep) decides what gets to run on it.
Apple has made the decision to follow the console model rather then the PC model. That is their choice. Your choice as a consumer is whether you choose to buy it or not. Your choice is NOT to force Apple to go another way other then through voting with your dollars.
Why has Apple made this decision? One of the many stupid mistakes MS has made in its lifetime is to allow Emails to contains executable code. For the email reader, the application to run external code. Abobe is regularly blamed for doing the same with PDF's. Lots of people here claim that data should not contain code. So when Apple decides that it does not want the option on ITS platform for 3rd party apps to run totally unknown 4th party code, of course they are COMPLETLY wrong in doing so...
Apple has made a reputation for itself by having a better, more solid, hassle free user experience. But how has it gotten this? Partially by its users being UNABLE to install the crap they do under windows. IF the mac platform got the same kind of malware and cripple ware attention as the PC, it would be just as bad an experience, with DRM overwriting sectors on the HD it has no business overwriting.
Is Apple right in believing that a controlled environment makes for a better user experience? Who knows, what I do know is that they sell millions of iPhones. People are voting with their dollars. Apparently they like SOMETHING about the iPhone more then they don't like.
Don't buy/develop for a closed platform and then complain it is closed. That is like breaking into a prison and then complaining they won't let you go.
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
The Briefs code is now up on GitHub, and yes, you can go look at it, however it's not "Open Source" (per OSI), it's not "Free Software" (per the FSF), and it's not "DFSG-free" (per Debian).
If you look at the commit history for the license, he even explicitly changed the license two days ago to make it less free:
2010-08-28
Modified license terms to disallow someone from reselling Briefs without making major modifications. Also protect the Briefs trademark. Still, free source code, huh? Not too shabby.
Prior to two days ago, the code was under the... well, I'm not exactly sure what license!
Here's the license (the first paragraph is a dead ringer for the opening of the MIT License):
Copyright (c) 2009-2010, Rob Rhyne
Briefs is a trademark of Digital Arch Design Corp.
http://robrhyne.com/
http://digitalarch.net/
All rights reserved.
Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without
restriction except as noted below, including without limitation
the rights to use,copy, modify, merge, publish, distribute,
and/or sublicense, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
Here's the non-FOSS part:
The Software and/or source code cannot be copied in whole and
sold without meaningful modification for a profit.
This is more of the MIT license:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
This middle part looks like the BSD license:
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with
the distribution.
Actually, there are only two clauses there, so that's essentially the 2-clause BSD, not the 3-clause one (just a minor point, really).
Then we get the YELLING-AT-YOU indemnification clause. Lawyers seem to love these things, but they seem so uncouth to me. Anyhow, for 5 points, from which license was this paragraph chosen?
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
That's right! It's the indemnification clause from the MIT license.
I googled around trying to figure out if other people used this same license, but the best I came up with was the NCSA license. It's unlikely that this license is based off that one, as the phrase to deal in the Software (MIT) is used in this new license instead of to deal with the Software (NCSA).
One more thing: let's point out exactly why the license doesn't pass any of the most popular FOSS metrics:
1) "Open Source" (per OSI)
Per
coding is life
How many more people does Apple have to hurt before it starts to tarnish the brand?
Apple has done a fabulous job of polishing the iPhone and iPad. If you really want the best available phone, and you aren't too choosy about your freedom, you buy Apple.
Sure, they won't get my money because I refuse to pay a company to tell me what software I may and may not install on my own device. That's okay, they don't care about me. But the more time goes by, the more stories like this one come to light. How much of this before people start to view Apple not so much as the hip, cool company but rather as the controlling, evil company?
And stories like this one are inevitable, because Apple is exerting such a high degree of control. The approval process isn't a simple rubber-stamp thing. The more innovative and unusual an app is, the harder it is for Apple to decide whether it gives the user too much freedom. In this case, I would guess that the problem is that an app for mocking up new apps is a little too much like an emulator, and Apple can't quite make up its collective mind whether this is a sort of emulator or not. (I can't even guess why Apple approved other app mockup apps while letting this one languish.)
So, the more time goes by, the more wronged people there will be. I guess as long as the majority of Apple customers are happy, and the majority of app developers aren't mistreated too much, the Apple brand will be undiminished.
But you know, if he had released his app for Android, it would be on the market now. He could even make an Android app for mocking up iPhone apps! I wish he would, just for the irony value.
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely
1) Fanboyism/zealotry. Apple has had a following for a long time of people for whom they can do no wrong more or less. A non-trivial amount of these people are in the press (Macs are big in prepress work). They just love Apple and everything they do. So when something bad comes out, they find ways to rationalize it away, or ignore it.
So we're in agreement here? This is yet moar evidence of the elite liberal media slant!
+= E
which is reason why, if they filmed the famous 'sledgehammer through the screen' commercial today
it would bounce right off with nary a scratch...
and how accurate an analogy it would be as well..
every day http://en.wikipedia.org/wiki/Special:Random
Nah. It's okay. Read at -1 and skim. Still lots better than most everyplace else.
1. Get app rejected by Apple
2. Generate attention by complaining about Apple's draconian policies
3. Resubmit app with required changes & Profit!
---
DRM is like antifreeze, to the MPAA/RIAA it's sweet, to the consumers it's poison.
This makes me wonder, how well could an app do on Apple/Android markets if it were open sourced as well? Those with the skill could download and compile it themselves, or those without (or wanting to donate) could pay 99 cents for it. Do the developer agreements for either side put restrictions on the source code? It'd be an interesting experiment to try.
Clever. :-)
You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
Some sheeple need iPhones to be cool. Just like other sheeple need to deride iPhone users to be cool.
You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
I agree with the primary idea above, but wish people would stop conflating languages and implementation details.
JavaScript/Java/Python/Lisp/PHP/C# are languages. Interpreted code is a method commonly used for early implementation of languages, and it is usually replaced by better methods as implementations mature.
Saying that language X is inherently slow because "it's interpreted" is wrong, but sounds superficially convincing enough to allow pointy-haired people to reject languages without really understanding the issues.
To a Lisp hacker, XML is S-expressions in drag.
http://github.com/capttaco/Briefs/commit/7124127274d77e5aba899049072cbd68d82cc048
I'll take the license/release checked in that has fewer restrictions, thank you very much!
Copy/archive at will.
"During times of universal deceit, telling the truth becomes a revolutionary act" -- George Orwell
it doesn't give any 1 user more than a few mod points because 1 user shouldn't have too much power,
Not sure why, but I have been given 15 mod points every two to three days 5 times in a row now.
That after a span of about 4 or 5 months with none.
I sure have no idea what system they're basing assignment on.
Apple doesn't "lead" the market. They produce a proprietary, closed-scale system
Closed is such an ugly word, and Apple knows this. For example we see that these days they prefer to use obscure, unused but open standard ports (and other trickery like their secret charger resistor trick), so they can get some of the lock-in effects of using proprietary ports without the bad PR.
If their lock-in becomes any stronger, expect 2.5mm instead of 3.5mm audio jacks in the future, for, uh, miniaturization purposes. They really need those millimeters. Hey, don't complain, it's an open standard.
You can probably expect to see some OOXML-ish stuff happening on the software side too. They're already trying the EEE approach with HTML5.
Closed is bad for PR and open is bad for keeping customers locked in. Pseudo-open gives you most of the benefits of both systems (decent lockin + negligible amounts of bad PR) with almost none of the downsides. Microsoft has known this for a while, Apple's just catching on.
"When information is power, privacy is freedom" - Jah-Wren Ryel
Dude, we commonly emailed uuencoded executeables back in 1992.
Second, we have the right to complain lsabout inconsistent bad rules by apple. What will it take, a wikileak by employees showing their procedure manuals?
Liberty freedom are no1, not dicks in suits.
autistic ;->
thank God the internet isn't a human right.
steve jobs
steven jobs
stephan jobs
stephand jobs
steph hand jobs
stiff hand jobs pees in your a-hole.
i-phone
i-phoney
I phoney stiff hand jobs pees in your a-hole.
i-fad
i-prod
can you flash-a mac?
Mac OsX
Mac Osex
Mac 0 Sex
Mac = zero sex.
thank God the internet isn't a human right.