Update iPhone app info without going through apple - iphone

i was wondering, i have a little experience making iPhone apps but no coding background in anything and was wondering.... Is there a way to update your iPhone app with new text, pictures, colors, links, etc. without manually doing it from Xcode then having to get the new version approved by apple.
I was hoping to be able to update it from possibly from my website. Any easy way to do this? Preferably the easiest solution. Thanks in advance

There is, but you have to design the application to do it from the start. Instead of reading from the app itself, the app reads from a content management system (CMS) or even just a text file stored on your website. Many apps work this way, but you will need to design the app with this in mind.

For the amount of things you need updated, I would create a iPhone optimized version of your website and in your app, all you would need is a web view that takes the user to your website. So to change content, you could just change your website and the user will think that the app is getting updated. One thing to keep in mind though, if the user doesn't have internet connection or if there internet is slow, the site my not show up at all or be very slow to respond and load. Hope this helps.

Related

Automatic Update of IPhone App

I am new to iPhone automatic updatability feature where user can change their contents whenever they want and iPhone app should pick them so that one need not to resubmit the application into Apple store. I know that I will need to deal with the database here a lot but if someone could through their idea on the solution design, implementation, and things to be taken care then that would be really helpful to me.
Thanks.
"content" here really means data. Apps can load data over the net to their hearts' content, but they can't load new code. Now, certain data might cause the existing code in the app to do one thing or another, so the app's behavior can be influenced by the data it uses. Don't play too close to the line, though -- if your data is really some form of scripting language that directly drives the behavior of the app, that will likely be deemed unacceptable.
As far as loading the content goes, there are a number of options available. The most common is probably using NSURLConnection asynchronously to load data from a web server. What the app does with the data after that is up to the app designer, and I don't think there's one objectively correct answer to that sort of question.
Apple not only allows this, but presented a session on this data driven app design technique at WWDC 2010, which is available as a video from iTunes to enrolled iOS developers.
Of course, the downloaded "content" can't include executable code, but it can include JavaScript and HTML5 to be run inside UIWebViews, as well as images, sounds, text, databases, etc., which can all be stored for offline use.
This violates apples SDK Agreement and will likely get your app removed from the app store if caught.
It should be mentioned that web apps offer the ultimate in automatic content updates. You can change the content, structure, and features of a web app without ever having to submit your app to Apple or anyone else. Deploying the app is as simple as copying a set of files to your server, and users get the updated version immediately, even if they're currently using the app. Web apps aren't a perfect solution in every case, but their capabilites are compelling if your app is dynamic.

Some questions about the App Store review guidelines?

I've made some iphone webapps before, using jQTouch and iUI but now i want to try out making a native Apps for iPhone. As i first step i thought of trying to port one of my webapps using Phonegap. So far it works well, but i'm a little concerned about some things in the Apple Review Guidelines and wanted to see if anyone have prior experience and could answer som questions.
2.5 Apps that use non-public APIs will be rejected
2.6 Apps that read or write data outside its designated container area will be rejected
I'm not really sure what this means. I don't think they concern me but if anyone could give me som more info about it it would be nice.
2.7 Apps that download code in any way or form will be rejected
This one is more tricky. Do they consider HTML code? What my app does is to load content into DIV-tags using jQuery.load()-function, that means much of the work in the app is performed on my server. Will it be "safer" if i generate JSON or XML of the data and process it with JavaScript inside the app instead of loading the formated HTML-code?
2.12 Apps that are not very useful or do not provide any lasting entertainment value may be rejected
This one together with the quote:
If your App looks like it was cobbled together in a few days, or you're trying to get your first practice App into the store to impress your friends, please brace yourself for rejection. We have lots of serious developers who don't want their quality Apps to be surrounded by amateur hour.
Made me wonder what they consider a useful app and what lasting entertainment means. This is my first app and i dont aim for a broad audience, this is mostly a way to get to know the XCode, iPhone-development and the App Store review process before. However, the App will be really useful for me and a bunch of my friends.
2.6 Don't specifically try to access files outside your app's Bundle or Documents directory and you should be fine.
2.7 Somewhere, it explicitly says you can download and use HTML/CSS/Javascript as long as you are running it inside an iOS UIWebView container. But don't try to download, say, Lua source code at runtime and interpret it.
2.12 Don't waste the App store reviewer's time if you are just trying to "get to know" the app development or store distribution process. Read about it instead. Submit something only if you think there are people (not just your Mom) who will really want to download your app and not delete it after trying it out. Maybe at least a dozen to hundred someones. If not, distribute some Ad Hoc deployments to your buddys instead.

can you install an iphone app with an invisible icon?

So I am working on a bundle of applications for my company for the iPad and am trying to figure out if it is possible to install an app but hide the icon. It will not need to be launched from the desktop directly. Instead, I have created a launch desktop that controls login and the launch of the actual apps via custom URL schemes. We decided to do this so we can have many people developing different apps at the time time that quickly and easily connect to a single login and launch desktop. We are trying to make all of the services we offer interconnected.
Does anyone know if this is possible? Or am I going to have to redirect to the login app if the user launches any of the individual apps. That is what we were trying to avoid. It would be incredibly annoying and clunky for the user. Any help would be greatly appreciated! Thanks!
No is the short answer, you can't install an app and hide the icon.
Even if you could, your architecture sounds pretty clunky. If your services are interconnected, then would it not be better to have everything in the same app? There are plenty of ways to share coding between many developers without everyone having their own, separate app.
Maybe.
There used to be a trick where if you installed so many apps that you filled up every page, any apps installed after that would not have a visible icon (but you could run them via a Spotlight search).
If this behavior still exists, then fill up your iPad's launcher/springboard with apps (download 100's of free games, etc.), then install the apps that you want to be invisible, then delete all the games, and your chosen app might remain with an "invisible" icon.

What are the wise and allowed ways to add advertisement to iPhone App?

I will be publishing an App in a few days. Initially I don't want to add advertisements, but can change my mind anytime, so I've thought this. Add a WebView to application and set its image to a dynamic web content. If no ads; I will display a simple logo, but when ads are available, replace the content with them. So there will be no modification to iPhone compiled binary.
Do you think it is allowed by Apple, and a good approach?
If you follow that approach, you will need to at least explain to Apple when you submit the app for review that ads may be enabled via a webservice.
Apple won't like it if you don't tell them that you might modify the apps feature set or behaviour after its approval.
You should be OK as long as you tell them about it.

Is it OK , from a product perspective, to write an iPhone app completely in WebView?

This just saves time.
Since I already have a web applciation.
I can just stick it inside a webview.
The question is: Does it turn off many users? How many users will be disgusted that the entire iPhone app is written in WebView?
I think it's pretty safe to say that most iPhone users are expecting apps to use the power of the iPhone, not just be a portal to a mobile website.
Think about facebook mobile compared to iPhone facebook app. If you're an iPhone user, I'm assuming you'd much rather use the app than a mobile version of the site (or mobile version of the site contained in a WebView in a an app).
That being said, depending on your app, if the mobile version of your app is highly usable, it could be okay...
Just my thoughts...
John Gruber on Daring Fireball just wrote about this today.
From a usability perspective, native apps usually feel better. They may also be more responsive and handle large amounts of data more gracefully. I have a few so-called "apps" on my devices which are just glorified Web apps, and they don't necessarily scream quality.
If you've already done your app, then just ship it. But keep your mind open to feedback from your users.
The answer is almost certainly "no". People care far more about the usability and experience of interacting with your application than what API-supplied widget you use to render it.
I read Apple has begun removing apps that are like this. Well technically, they remove apps they think could be easily implemented as a webapp instead. Yours obviously qualifies ;)
Source: http://techcrunch.com/2010/03/07/apple-cookie-cutter-apps/
EDIT: Apple seems to not mind, according to the Human Interface Guidelines:
If you have a webpage or web application, you might choose to use a web view to implement a simple iPhone application that provides a wrapper for it.
Of course, Apple has a tendency to contradict themselves. ;)
Apple human interface guidelines says this isn't even allowed. I forget where it comes from, but somewhere in the guideline it says apps that are only web views are not allowed. I'm about 95% sure I've seen this. Can anyone confirm?