I an new in iphone application i want to put Nevigation controller after a splash screen so how can i put?Is there any way to put nevigationbar in my application without Splash Screen.
The recommended way to get a splash screen* is to use Default.png - this is the image that the iPhone puts on the screen while your app starts up - see the apple docs for more information.
And to get a basic navigation controller application running, the easiest way to see this is to make a new project - in Xcode choose File->New Project and then choose a Navigation Based Application - this will make a new project that has an empty Navigation Controller.
If you want to get the splash screen to stay on for longer, see the answers to this question
Hope that helps,
Sam
*Actually, the apple docs want you not to make a splash screen but to make a screenshot of the first page of your app so it appears to load faster - very few people do this, most make a splash screen and apple don't seem to mind too much.
Related
I have a splash image that I want to display when the app is launching. I use it as a launch image - I want it to be displayed until the program is launched (rename the picture to Default.png).
In apple's HIG they say one should "avoid" using a splash screen as a launch image.
I know it's not recommended and that users often don't like them, but will it make Apple reject my application? If so, how can I display a splash screen so it'll be displayed as soon as the app goes on, but not violate those rules? because I have seen applications with splash screens as launch images.
Thx in advance!
It's not that Apple will reject your App just coz you have a splash screen. But it's advisable to not have a splash screen as the user has to wait. Better not make the user wait...
Flipboard which was the Apple App of the year in 2010 has an image splash screen. As the user enjoys the images, data is downloaded in the background so that as soon as the user flips the page, the next screen is all ready & up to date. But they have made it in such a tasty fashion that the user hardly feels as if he's been made to wait. So it all depends on your design...
If you plan to simply use the Default.png mechanics to display your splash image, there is no problem.
The issue arises when you would like to prolong the display of such image only for the sake of it. This is what the HIG are against: that the user is made to wait without any real benefit. It is also to be noticed that with the advent of multitasking (iOS 4), the effect of showing a splash screen is reduced, since most of the times the app is not closed, so you see no splash screen at all when you go back to it.
On the other hand, it is understood that if you need to do some setup task in your app that take time and you have to do that at startup, then the user will have to wait. It is important, though, that he/she be notified of the wait and why it is for. This could mean, e.g., displaying a label on top of your image saying: "Loading..." or "Preparing data..." or whatever your user might better understand as part of the functionality of the program.
As to how to do it, there is no other way, AFAIK, than starting your app with a view that is exactly the same as Default.png (a simple UIImageView would do). That means, that in you appDidFinishLaunching delegate method, you create the view and attach it to the window; then, when you have done with your app preparation, you switch to your real view.
This would give you also the chance to add the label or whatever other kind of messaging to the user.
Can anyone provide me a sample code for adding a splash screen to an existing Xcode project. What is the better way to add a splash screen? I mean is it using model view controller or just adding the image in resource folder. And if I want to play any movie on the splash screen then how can I do it?
You are looking for Splash screen of video type right?
Go through these source code steps.
http://iphonedevcentral.blogspot.com/2010/08/display-iphone-movies-in-portrait-mode.html
Write your own Utility Class. And on Video Done clicked show your home screen
Code: http://iosdevelopertips.com/wp-content/uploads/2010/07/MoviePlayer-Portrait-Mode-ios4.zip
I'm going to submit a Lifestyle app to the App Store. I'm confused whether to add a Splash Screen to the App or not ?
Please advise me whether it's a good or bad idea as far as usability and App Store's submission guidelines are concerned.
Its bad - you shouldn't do that!
Please read the Start Instantly Section of the Apple HI Guidelines
Avoid displaying an About window or a
splash screen. In general, try to
avoid providing any type of startup
experience that prevents people from
using your application immediately.
http://developer.apple.com/library/ios/#documentation/UserExperience/Conceptual/MobileHIG/UEBestPractices/UEBestPractices.html
You should definitely at least add a Default.png to your app if I understand your question correctly.
Launching an app and looking at a black screen for a split second is not the best user experience. Some nice-looking image with your company name or app logo will do. Or you could follow Apple's guidelines and present an image of the starting user interface so that your app will seem to load instantly.
Here's a relevant doc.
The developers guides mostly suggest a splash that looks like the starting screen of your app, to give people the impression the app has started. This has the bonus of allowing the user to start figuring out what they want to do while the program finishes loading.
From a users standpoint, I dislike most splash screens, I just want to get to the program, not look once again at what constitutes an advertisement for the program.
if your app loads blazingly fast,then you can provide this method in
- (void)applicationDidFinishLaunching:(UIApplication *)application
[NSThread sleepForTimeInterval:3];
Before your view controller is loaded.
It will halt the main thread for 3 seconds,which will give time to your splash screen.Thats the way i do and there is no problem with this method,as you are working on the main thread.
Yes, you can add a splash screen to your app.
Depending on what you do with your splash screen as far as extravagant animations go, I would go subtle, with minimal animations.
You can add a Default.png (see iOS documentation!) to your application bundle.
This image is being shown full screen while your application is loading.
Other than that, I wouldn't add a splash screen to your app.
ok. I know how to display the splash screen on iPhone. Seems quite simple enough (i.e. setting the Default.png and calling "sleep" command).
But, is the application actually doing anything during this time? My app needs to go and fetch some data from Web before showing the app's first screen, but when I do the splash screen, it doesn't seem like it's doing this while showing the splash image.
Can I actaully make the app do something while showing the splash screen?
The best way would be to structure you application differently slightly differently.
Make your application display the Default.png when it starts it (ie. put a UIImageView onto screen), then start fetching your data.
Then either when you have fetched the data (or if you really must, once an NSTimer has expired, but it's a better user experience if you avoid a fixed time interval) change the view to be your real one.
Where you have got the idea that you need to call "sleep" while showing Default.png and there is nothing going on while this image is shown? Default.png is shown when OS is loading your app. You can not do anything during this time. In fact you have not got any control yet. It is handled by the OS. The idea behind this is to give user a feeling that app has loaded quickly, but actually your app is not completely loaded while Default.png is showing instead of a black screen by the OS.
You can manually add a view looking like your splashscreen after starting your app and handle the work in background. I would also add a hint to the user which indicates "loading data", because an app should start within 3 seconds.
If you read the Human Interface Guidlines, they're pretty clear that Default.png isn't intended to be a branding splash screen. It's meant to bring up a static "shell" of the initial page of UI so that the user experiences quick loading. So it's not at all designed or intended for what a lot of apps are using it for (including some of mine).
If you have your first screen that comes up be that image again, maybe with an activity spinner or status text on it, you can do whatever you need to do in the background of it, and then replace it with the first "real" screen of your app when you're done.
Generally all of the awakeFromNib calls in view controllers are done while the app is loading (ie has the splash screen up). When I put breakpoints in my apps at awakeFromNib calls, the breakpoints are hit when the splashscreen is up and the app is loading. So everything you do in
those calls will be processed while the loading screen is up.
Is it possible to make the iphone app splash screen pick up a random image or text? So that it is different every time (e.g. display tips)? If so how?
This is not possible. The Default.png file in your application is always the "splash screen". To try and alter it after the application has been built would alter the signature of your application, and it would not launch the next time it was run. (Assuming you can write to files within your application bundle, which I have not tried.)
It is true that you cannot alter the splash screen, but you can present a view with whatever you want in it. Don't include a Default.png image in the bundle. Then in your app delegate, instantiate a view controller and add it's view as a subview to self.window. Then you need to dismiss this view, either based on a timer, or the completion of your startup processing, or a user tap, etc.
It is worth noting that Apple discourages using a splash screen, and recommends that you just get the UI up and working as fast as possible. If you must have a splash screen, you can display something that looks like your working app to create the illusion of a responsive UI, and remove that as soon as your UI really is responding.