on their website they have "announcements" made at various times saying that it is either prohibited or allowed. The latest announcement, as of September 2010, seems to say that it is allowed, but then maybe there are some more that I haven't located prohibiting it.
So what is the final truth of the matter now? Does Apple marketplace accept RunRev stuff or not?
The latest announcement is correct, and Apple is permitting apps built with [Livecode/Rev/whatever we're calling it this year] in the iOS App Store. The first one, I think, was Sheep Herder, but there are others.
Apple had initially said this was OK, then changed its mind during the Great Steve Versus Flash Incident of 2010. (Rev was collateral damage, along with all other non-Apple development platforms). Then it changed its mind back. So the situation changed several times before it stabilized, which is why the Rev blog and forum archives have different announcements at different times.
As a further development, LiveCode iOS apps built with the forthcoming open source licensed LiveCode will not be allowed in the App Store because of licensing issues. Apps developed with the commercial license (paid) LiveCode will still be accepted.
There are very many more than just Sheep Herder in the app store - I ran a survey a bit over a year ago (November 2011) and some 40 people sent me appstore links to their apps.
You can see a bunch of stuff-built-with Livecode, including a number of apps, here:
http://livecode1001.blogspot.co.uk/
Related
I just want to ask that how can i develop apps for Nokia 220 which has s30+ platform. Is there any way to develop apps for this or not?
It appears that the answer is no.
In spite of the name, S30+ is not related to S30.
Microsoft's specifications page for the Nokia 220 mention a handful of built-in applications (browser, calendar, contacts, alarm clock, "native games", etc.), but says nothing about installable applications.
This FAQ: How do I update the software on my Series 30+ phone? discusses a "Software Recovery Tool" that runs on a computer; it erases all personal content on the phone.
This doesn't prove that it's impossible to install additional applications, but it strongly suggests that it's at least not supported.
S30+ is MRE from Mediatek, see mre.mediatek.com.
There you can find a development system.
However, for the Microsoft handsets you need signing,
which i dont know how to achieve.
Sorry for being late for nearly 7 years (I was a kid 7 years ago :D)
Here is the link to a comment on Github where a man post a copy of MRE SDK 3.0.
From his comment:
Yes it is removed from his server bit I have copy of it on my google
drive I give you link
https://drive.google.com/file/d/1KIh3VrOIAYLVw5cOf2_uPQvJbOmT6MyC/view?usp=drivesdk
and
If you want any other software that are missing you may found here
https://drive.google.com/folderview?id=12ohq-7V0_02QQX9Kjf1m6YRWHO9-JpPy
If the link is broken, leave a comment and I will fix it :)
I also made a copy of it in my repo.
Hope it helps.
My employer has a free iOS app in iTunesConnect that was originally released a couple of years ago and has received various updates over time. They now wish to stop supporting older versions of the application (1.x) and disable these older versions of the app.
My questions are:
Can we stop users from re-installing old versions of the app? If yes, how?
How do we disable/remove old versions of the app in iTunesConnect?
What is Apple's policy regarding disabling/removing old versions of applications?
I'm not an iOS developer and am unfamiliar with the whole Apple application development process. I have searched the web as well as the Apple developer centre and I've read through the Apple Developer Program Terms and Conditions but I haven't been able to find answers to any of my questions.
I have managed to find information about removing an application from sale but this removes the entire application, rather than just specific versions. (Deleting a free app from iTunesConnect)
David Smith's article (http://david-smith.org/blog/2012/06/20/hacking-paid-upgrades/) on Paid Upgrades mentions the ability to provide fixes for previous versions if they're not deleted from iTunesConnect. When I log into iTunesConnect, I only see the current version of the app listed so I'm assuming prior versions have been deleted already. I would, however, like to confirm that users can no longer download old versions of the app.
This article mentions users being able to download old versions of apps from iCloud (http://www.macrumors.com/2011/06/09/icloud-supports-re-downloading-some-discontinued-apps/) - can we prevent this? One option would be to mark the the version as having a "legal issue" but what ramifications does this have? and if I can't see the app in iTunesConnect then how do I do it?
I found a post asking about how to force a user to upgrade the application every time a new version is released but this doesn't answer my questions either. We want the users to upgrade but we're not wanting to force it programmatically. (Can I force an iPhone user to upgrade an application?)
I've also found lots of posts asking how to revert to previous versions of an app in the app store but again, this is not what we're wanting to do. We're wanting to disable older versions of the app but leave the most recent versions alone.
Before the flame wars begin:
Users that are unable to update to the latest version of the app for whatever reason are able to use a mobile website in place of the app. The website has the exact same functionality.
Can answers please be kept on-topic rather than getting into great debates over whether one should/shouldn't maintain legacy versions.
Thanks in advance :)
Users can typically only ever download the latest version of an application. There are a few ways I think they can get around that but in general only the latest version is available to users via the normal means.
If, however, you absolutely must prevent the old versions from being released you can do so when submitting a new update. Right after you say "Ready for Upload" you will be asked a question about if this update was for a 'legal reason' if you click YES then you will be given the opportunity to disable old versions of the app from download.
As to Apple's policy on this...I have no idea. But I can't think of any policy that would require you to support older versions moving forward.
Can someone provide concrete info on how the app upgrade process works on iOS as far as the developer is concerned? I've been rummaging through Stackoverflow only to find hand-waving explanations and no links to official documentation. Google search results only led to Cisco's IOS and the end-user upgrade process. I'd like to know the following:
How does the App Store know when you've provided a new version? Do I have to implement something in my app, which the App Store pings? Or do I set things up stuff through the Apple Developer website? I've been waiting 2 months for developer approval and have no idea what's going on behind those doors because I get access-denied messages when trying to read official articles.
Is there any Objective-C code I need to write for an upgrade to be possible? Any plist I need to edit?
How is payment affected when version 1 of the app is free, then version 2 is paid or version 1 is paid and version 2 changes its price.
Does Apple allow me to do forced upgrades? All the answers on Stackoverflow have been, "I think this is bad business logic" or "I think Apple forbids this, but I don't have the official documentation to prove it." At a certain point, very old versions will be too time consuming to support. You don't see Microsoft still supporting Windows 95, do you?
You just submit the new version to Apple. When it's approved, it will appear in the App Store.
Same as above, Apple pretty much does it all for you.
If you transition from free to paid, everyone that has downloaded the app for free will not have to pay to upgrade to the paid version.
IIRC you cannot force users to upgrade, but you can display a notification within the app to alert users that an update is available. To implement this, I would just have the app request a file on your server that tells the app what the current version number is. You do not need to support users on old version, if they have problems with an old version, it's fine to tell them to upgrade.
I have a C# application which needs to be ported to several Smartphones. Monotouch looks like the best choice for the IPhone, if there wasn't section 3.1.3 in the new developer agreeement.
Now the Monotouch website lists 3 Monotouch apps that were allowed to the App store after the new agreement was put in place. Was it just pure luck for their developers, or is Apple actually not enforcing section 3.1.3 except with regards to Flash applications?
Thanks,
Adrian
The only people who can actually answer this question work for Apple, and they're not going to tell you.
I believe that MT is compiled to native code in such a way that it's not possible (within reason) to determine that it wasn't written in native obj-c in the first place.
And I haven't heard of any MT apps being rejected specifically for violating 3.1.3.
allow me to end this for all of you!!!
http://www.apple.com/pr/library/2010/09/09statement.html
As a MonoTouch developer with apps in the iTunes store (for example http://escoz.com/cracklytics), I can tell you that Apple is currently accepting MonoTouch apps normally. They approved 2 recent updates I did to the app with no issues.
Regarding new apps, lots of people in the #monotouch irc channel also have their new apps approved every other day, with no issues. Nothing changed because of 3.1.3 so far.
I wrote more about it here: http://escoz.com/monotouch-is-alive/ . Neither Apple or Novell have really mentioned anything regarding an agreement, so nobody really knows if they now have one or not.
Apple amended 3.1.3 to allow you to ask for an exception for your application. That might be what is going on, or architecturally it may not matter to Apple.
Will CS5's Packager for iPhone still be an option when CS5 comes out? Or, will any apps submitted to the App Store be denied because of the new restriction that the app has to be written in Objective-C, C, C++, and/or AppleScript(?)?
The second answer is correct: such applications will be denied. Indeed, there has been ample speculation that the very purpose of the new developer agreement is to stop Packager's spreading, because Apple really wants to limit iPhone apps to native ones.
The answer to this question has changed
Special Update: September 9, 2010
Apple’s recent announcement that it has lifted restrictions on its third-party developer guidelines has direct implications for the Packager for iPhone. The feature is available for developers to use today and Adobe will now resume development work on this feature for future releases.
http://labs.adobe.com/technologies/packagerforiphone/