Recently in iPhone Development Category

Apple Force-Choke Relaxed: Here Comes the Third Party!

| No Comments | No TrackBacks
App Store

Image via Wikipedia

Today, Apple announced two things. Both of which are important developments for the Apple Dev community. The first and possibly least prominent part of their announcement today is this:

"In addition, for the first time we are publishing the App Store Review Guidelines to help developers understand how we review submitted apps. We hope it will make us more transparent and help our developers create even more successful apps for the App Store."

This is great for developers. Before, Apple's App review process was, shall we say, behind closed doors. People would submit apps, not hear about them for weeks at a time, and then finally get a note back from Apple saying their app had been rejected for some stupid little thing that the developer didn't know was being checked for. Now however, Apple is actually publishing their guidelines for their app review process. Hopefully this will help the developer community get less rejections from the store and have their apps availible on the App Store quicker. 

The other development today is that Apple has made changes to the famous "Section 3.3.1" of their iOS developer agreement. They state:

"We are continually trying to make the App Store even better. We have listened to our developers and taken much of their feedback to heart. Based on their input, today we are making some important changes to our iOS Developer Program license in sections 3.3.1, 3.3.2 and 3.3.9 to relax some restrictions we put in place earlier this year.

In particular, we are relaxing all restrictions on the development tools used to create iOS apps, as long as the resulting apps do not download any code. This should give developers the flexibility they want, while preserving the security we need."

This is huge. This ends the long fought battle between Adobe and Apple over the Flash iPhone packager. Now, anyone who wants to can use Flash CS5 Professional to develop iPhone apps to sell to the public. In all, amazing!

But this makes me wonder. Why did apple all of the sudden decide that it was okay for other people beside XCode developers to publish for the app store? Is it Android taking over it's market because it has Flash Player? Possibly. I believe that this is Apple's way of rebounding against android and an attempt to block android from taking over more of its market. Also, could this be a sign of things to come for iOS? Flash Player, maybe? It's too early to tell. 

I want to hear your opinion! Leave a comment letting me and everyone else know what you think about this development in the Apple world. 

All for Now!
Enhanced by Zemanta

Apple vs. Adobe - The Battle over 3.3.1

| No Comments | No TrackBacks
n113492765344092_7540.jpgBy now, I'm sure everyone has seen or at least heard of the language in the iPhone SDK 4.0 agreement that appears to make developing an iPhone or iPad application in anything other than XCode a violation of terms. This obviously has sparked much harsh debate over development in things other than Xcode. Several different platforms such as Titanium Developer, PhoneGap, and even the upcoming Flash CS5 will also have iPhone development built into it. Well, what could apple possibly be trying to do here? Shut down all development outside of XCode? Well, obviously they are. But to what end? That's what a lot of people are asking right now. When asked about it in a dialogue with Greg Slepak of the Tao Effect, Uncle Steve said that they inserted this clause into the developer agreement because:

"intermediate layers between the platform and the developer ultimately produces sub-standard apps and hinders the progress of the platform"

I'd like to ask this of Steve. What apps are you talking about? Show me one application built on something other than Xcode that "hinders the progress of the platform". If this is really the case, then apps like Firefox and Chrome hinder the progress of the Mac platform. Obviously they don't; rather they aid it in it's progress. And I'd also like to see one sub par iPhone app that has been accepted into the app store that was built in a different environment. Especially some of the ones built on Flash. I'd like to see some of those that can be proven by Apple to be "sub par". I don't think they can find one. Show me one Steve, and I might believe you. Otherwise, I'm definitely with Adobe. 

All for Now!
Reblog this post [with Zemanta]

iPhone Dev and Flash CS5

| No Comments | No TrackBacks

At Adobe MAX today, it was announced that the new version of Flash Professional, which will enter public beta before the year is out, will now have an exporter for iPhone. Yes, that means that Flash applications will finally run on the iPhone. Here is a short video describing this new technology.


,,,,

Apple responds to the FCC

| No Comments

I know it's been a while since the Apple-FCC conversation over the google voice app, but here's the text anyway. this text retrieved directly from Apple.com.

Today Apple filed with the FCC the following answers to their questions.

We are pleased to respond to the Wireless Telecommunications Bureau’s inquiry dated July 31, 2009, requesting information regarding Apple’s App Store and its application approval process. In order to give the Bureau some context for our responses, we begin with some background information about the iPhone and the App Store.

Apple’s goal is to provide our customers with the best possible user experience. We have been able to do this by designing the hardware and software in our products to work together seamlessly. The iPhone is a great example of this. It has established a new standard for what a mobile device can be—an integrated device with a phone, a full web browser, HTML email, an iPod, and more, all delivered with Apple’s revolutionary multi-touch user interface.

Apple then introduced something altogether new—the App Store—to give consumers additional functionality and benefits from the iPhone’s revolutionary technology. The App Store has been more successful than anyone could have ever imagined. Today, just over a year since opening, the App Store offers over 65,000 iPhone applications, and customers have downloaded over 1.5 billion applications.

The App Store provides a frictionless distribution network that levels the playing field for individual and large developers of mobile applications. We provide every developer with the same software that we use to create our own iPhone applications. The App Store offers an innovative business model that allows developers to set their own price and keep more (far more in most cases) of the revenue than traditional business models. In little more than a year, we have raised the bar for consumers’ rich mobile experience beyond what we or anyone else ever imagined in both scale and quality. Apple’s innovation has also fostered competition as other companies (e.g., Nokia, Microsoft, RIM, Palm and Verizon) seek to develop their own mobile platforms and launch their own application stores.

Apple works with network providers around the world so that iPhone users have access to a cellular network. In the United States, we struck a groundbreaking deal with AT&T in 2006 that gives Apple the freedom to decide which software to make available for the iPhone. This was an industry first.

We created an approval process that reviews every application submitted to Apple for the App Store in order to protect consumer privacy, safeguard children from inappropriate content, and avoid applications that degrade the core experience of the iPhone. Some types of content such as pornography are rejected outright from the App Store, while others such as graphic combat scenes in action games may be approved but with an appropriate age rating. Most rejections are based on bugs found in the applications. When there is an issue, we try to provide the developer with helpful feedback so they can modify the application in order for us to approve it. 95% of applications are approved within 14 days of their submission.

We’re covering new ground and doing things that had never been done before. Many of the issues we face are difficult and new, and while we may make occasional mistakes, we try to learn from them and continually improve.

In response to your specific questions, we would like to offer the following:

Question 1. Why did Apple reject the Google Voice application for iPhone and remove related third-party applications from its App Store? In addition to Google Voice, which related third-party applications were removed or have been rejected? Please provide the specific name of each application and the contact information for the developer.

Contrary to published reports, Apple has not rejected the Google Voice application, and continues to study it. The application has not been approved because, as submitted for review, it appears to alter the iPhone’s distinctive user experience by replacing the iPhone’s core mobile telephone functionality and Apple user interface with its own user interface for telephone calls, text messaging and voicemail. Apple spent a lot of time and effort developing this distinct and innovative way to seamlessly deliver core functionality of the iPhone. For example, on an iPhone, the “Phone” icon that is always shown at the bottom of the Home Screen launches Apple’s mobile telephone application, providing access to Favorites, Recents, Contacts, a Keypad, and Visual Voicemail. The Google Voice application replaces Apple’s Visual Voicemail by routing calls through a separate Google Voice telephone number that stores any voicemail, preventing voicemail from being stored on the iPhone, i.e., disabling Apple’s Visual Voicemail. Similarly, SMS text messages are managed through the Google hub—replacing the iPhone’s text messaging feature. In addition, the iPhone user’s entire Contacts database is transferred to Google’s servers, and we have yet to obtain any assurances from Google that this data will only be used in appropriate ways. These factors present several new issues and questions to us that we are still pondering at this time.

The following applications also fall into this category.

  • Name: GVDialer / GVDialer Lite
    Developer: MobileMax
    info@mobile-mx.com
  • Name: VoiceCentral
    Developer: Riverturn, Inc.
    4819 Emperor Blvd., Suite 400
    Durham, NC 27703
  • Name: GV Mobile / GV Mobile Free
    Developer: Sean Kovacs
    sean@seankovacs.com

We are continuing to study the Google Voice application and its potential impact on the iPhone user experience. Google is of course free to provide Google Voice on the iPhone as a web application through Apple’s Safari browser, just as they do for desktop PCs, or to provide its “Google-branded” user experience on other phones, including Android-based phones, and let consumers make their choices.

Question 2. Did Apple act alone, or in consultation with AT&T, in deciding to reject the Google Voice application and related applications? If the latter, please describe the communications between Apple and AT&T in connection with the decision to reject Google Voice. Are there any contractual conditions or non-contractual understandings with AT&T that affected Apple’s decision in this matter?
Apple is acting alone and has not consulted with AT&T about whether or not to approve the Google Voice application. No contractual conditions or non-contractual understandings with AT&T have been a factor in Apple’s decision-making process in this matter.
Question 3. Does AT&T have any role in the approval of iPhone applications generally (or in certain cases)? If so, under what circumstances, and what role does it play? What roles are specified in the contractual provisions between Apple and AT&T (or any non-contractual understandings) regarding the consideration of particular iPhone applications?

Apple alone makes the final decisions to approve or not approve iPhone applications.

There is a provision in Apple’s agreement with AT&T that obligates Apple not to include functionality in any Apple phone that enables a customer to use AT&T’s cellular network service to originate or terminate a VoIP session without obtaining AT&T’s permission. Apple honors this obligation, in addition to respecting AT&T’s customer Terms of Service, which, for example, prohibit an AT&T customer from using AT&T’s cellular service to redirect a TV signal to an iPhone. From time to time, AT&T has expressed concerns regarding network efficiency and potential network congestion associated with certain applications, and Apple takes such concerns into consideration.

Question 4. Please explain any differences between the Google Voice iPhone application and any Voice over Internet Protocol (VoIP) applications that Apple has approved for the iPhone. Are any of the approved VoIP applications allowed to operate on AT&T’s 3G network?
Apple does not know if there is a VoIP element in the way the Google Voice application routes calls and messages, and whether VoIP technology is used over the 3G network by the application. Apple has approved numerous standard VoIP applications (such as Skype, Nimbuzz and iCall) for use over WiFi, but not over AT&T’s 3G network.
Question 5. What other applications have been rejected for use on the iPhone and for what reasons? Is there a list of prohibited applications or of categories of applications that is provided to potential vendors/developers? If so, is this posted on the iTunes website or otherwise disclosed to consumers?

In a little more than a year, the App Store has grown to become the world’s largest wireless applications store, with over 65,000 applications. We’ve rejected applications for a variety of reasons. Most rejections are based on the application containing quality issues or software bugs, while other rejections involve protecting consumer privacy, safeguarding children from inappropriate content, and avoiding applications that degrade the core experience of the iPhone. Given the volume and variety of technical issues, most of the review process is consumed with quality issues and software bugs, and providing feedback to developers so they can fix applications. Applications that are fixed and resubmitted are approved.

The following is a list of representative applications that have been rejected as originally submitted and their current status:

  • Twittelator, by Stone Design Corp., was initially rejected because it crashed during loading, but the developer subsequently fixed the application and it has been approved;
  • iLoveWiFi!, by iCloseBy LLC, was rejected because it used undocumented application protocols (it has not been resubmitted as of the date of this letter);
  • SlingPlayer Mobile, by Sling Media, was initially rejected because redirecting a TV signal to an iPhone using AT&T’s cellular network is prohibited by AT&T’s customer Terms of Service, but the developer subsequently fixed the application to use WiFi only and it has been approved; and
  • Lingerie Fantasy Video (Lite), by On The Go Girls, LLC, was initially rejected because it displayed nudity and explicit sexual content, but the developer subsequently fixed the application and it has been approved with the use of a 17+ age rating.

Apple provides explicit language in its agreement with iPhone developers regarding prohibited categories of applications, for example:

  • “Applications may be rejected if they contain content or materials of any kind (text, graphics, images, photographs, sounds, etc.) that in Apple’s reasonable judgment may be found objectionable, for example, materials that may be considered obscene, pornographic, or defamatory; and
  • Applications must not contain any malware, malicious or harmful code, program, or other internal component (e.g. computer viruses, trojan horses, ‘backdoors’) which could damage, destroy, or adversely affect other software, firmware, hardware, data, systems, services, or networks.”

And we also provide a reference library that can be accessed by members of the iPhone Developer Program that lists helpful information such as Best Practices and How To Get Started.

Question 6. What are the standards for considering and approving iPhone applications? What is the approval process for such applications (timing, reasons for rejection, appeal process, etc.)? What is the percentage of applications that are rejected? What are the major reasons for rejecting an application?

As discussed in the response to Question 5, Apple provides guidelines to developers in our developer agreement as well as on its web site regarding prohibited categories of applications. These materials also contain numerous other provisions regarding technical and legal requirements that applications must comply with, and Apple uses these standards in considering whether or not to approve applications.

Apple developed a comprehensive review process that looks at every iPhone application that is submitted to Apple. Applications and marketing text are submitted through a web interface. Submitted applications undergo a rigorous review process that tests for vulnerabilities such as software bugs, instability on the iPhone platform, and the use of unauthorized protocols. Applications are also reviewed to try to prevent privacy issues, safeguard children from exposure to inappropriate content, and avoid applications that degrade the core experience of the iPhone. There are more than 40 full-time trained reviewers, and at least two different reviewers study each application so that the review process is applied uniformly. Apple also established an App Store executive review board that determines procedures and sets policy for the review process, as well as reviews applications that are escalated to the board because they raise new or complex issues. The review board meets weekly and is comprised of senior management with responsibilities for the App Store. 95% of applications are approved within 14 days of being submitted.

If we find that an application has a problem, for example, a software bug that crashes the application, we send the developer a note describing the reason why the application will not be approved as submitted. In many cases we are able to provide specific guidance about how the developer can fix the application. We also let them know they can contact the app review team or technical support, or they can write to us for further guidance.

Apple generally spends most of the review period making sure that the applications function properly, and working with developers to fix quality issues and software bugs in applications. We receive about 8,500 new applications and updates every week, and roughly 20% of them are not approved as originally submitted. In little more than a year, we have reviewed more than 200,000 applications and updates.

Looking to develop for iPhone?

| No Comments | No TrackBacks
One of the best resources that I have found if you want to learn how to develop for iPhone is found on iTunes U. The provider is Stanford University, and it is actually one of the classes that they offer, recorded and posted. CS-193P, to be exact. The class is taught mainly by apple developers, and is for everyone of all skill levels. It takes you through all of the basics for developing, and really teaches you well. I've found it to be a valuable resource that everyone should check out!

All for now!

iPhone Development on a Powerbook!

| No Comments | No TrackBacks
When Apple announced that it's iPhone SDK would not be supported on a PowerPC mac, many developers were highly disappointed. I was one of them. Well, it turns out that the iPhone SDK 2.2.1 and before, not 3.0, are actually universal binaries. It only took a few days for people to figure this out. Here's a detailed description of what do do from the Apokalypse Software Corp. 

Here's how you can install the iPhone SDK for 2.2.1 on a Mac running at least MOX 10.5.5:

1. Ensure you have at least 6 gigs of disk space available. If you have tried to install the iPhone SDK on the target volume before, it may state an upgrade will be performed instead of an install. Sadly, the only solution I currently have for this situation is to uninstall Xcode using /Library/Developer/3.1/uninstall-devtools.
2. Download the SDK disk image.
3. Mount the image by double-clicking it.
4. Copy the mounted volume to a hard drive.
5. Navigate to iPhone SDK.mpkg/Contents/iPhoneSDK.dist in the copied folder and replace line 340 which should be
start_selected = "isIntel() && hasRightOS() && agreedToSLA()"

with
start_selected = "true"

6. Run the installer, selecting either the default location /Developer or another directory name if you're looking to preserve your current Xcode installation.
7. After a successful installation, navigate from the installation directory (default of/Developer) to/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Specifications/iPhone Simulator Architectures.xcspec, and make the following two changes.

First, replace

{ Type = Architecture;
Identifier = Standard;
Name = "Standard (iPhone Simulator: i386)";
Description = "32-bit iPhone Simulator architectures";
ListInEnum = YES;
SortNumber = 1;
RealArchitectures = ( i386 );
ArchitectureSetting = "ARCHS_STANDARD_32_BIT";
},

with

{
Type = Architecture;
Identifier = Standard;
Name = "Standard (iPhone Simulator: i386)";
Description = "32-bit iPhone Simulator architectures";
ListInEnum = YES;
SortNumber = 1;
RealArchitectures = (
i386,
);
ArchitectureSetting = "ARCHS_OLD_STANDARD_32_BIT";
},
{
Type = Architecture;
Identifier = Standard;
Name = "Standard (iPhone Simulator: ppc)";
Description = "32-bit iPhone Simulator architectures";
ListInEnum = YES;
SortNumber = 1;
RealArchitectures = (
ppc,
);
ArchitectureSetting = "ARCHS_STANDARD_32_BIT";
},

then, replace

{ Type = Architecture;
Identifier = i386;
Name = "Intel";
Description = "32-bit Intel";
PerArchBuildSettingName = "Intel";
ByteOrder = little;
ListInEnum = NO;
SortNumber = 105;
},

with

{
Type = Architecture;
Identifier = i386;
Name = Intel;
Description = "32-bit Intel";
"PerArchBuildSettingName" = Intel;
ByteOrder = little;
ListInEnum = NO;
SortNumber = 105;
},
{
Type = Architecture;
Identifier = ppc;
Name = "Minimal (32-bit PowerPC only)";
Description = "32-bit PowerPC ";
"PerArchBuildSettingName" = PowerPC;
ByteOrder = big;
ListInEnum = No;
SortNumber = 201;
},
{
Type = Architecture;
Identifier = ppc7400;
Name = "PowerPC G4";
Description = "32-bit PowerPC for G4 processor";
ByteOrder = big;
ListInEnum = NO;
SortNumber = 202;
},
{
Type = Architecture;
Identifier = ppc970;
Name = "PowerPC G5 32-bit";
Description = "32-bit PowerPC for G5 processor";
ByteOrder = big;
ListInEnum = NO;
SortNumber = 203;
},

Now go ahead and start Xcode and when you select the "File > New Project..." menu item, you should see a darling iPhone category for projects. Also, run the iPhone simulator in /(Xcode install path)/Platforms/iPhoneSimulator.platform/Developer/Applications/iPhone\\ Simulator.app, it's really mind-blowing to run it on your desktop, especially one Apple tells you isn't able to run their iPhone SDK.

End of Article-------------

I use this and it works great. Here's a screenshot of my computer running the iPhone Simulator 2.2.1 to prove that this actually works.

You should really use this if you're stuck on a PPC and want to make iPhone apps. It works Great!

About this Archive

This page is an archive of recent entries in the iPhone Development category.

Google is the previous category.

Loopholes is the next category.

Find recent content on the main index or look in the archives to find all content.