i implemented interstitial ad by using flutter, it shows without any problem but after user dismissed the ad, it takes approximately 5 second to navigate to the next page; Do anyone know the reason?
Related
I created a login screen using SwiftUI.
When I press a login button (after the validation of email and password), it navigates to a ViewController.
Login state is stored in a userDefault Boolean for use later when the app is launched again.
In SceneDelegate, userDefault is checked--if it istrue, the main screen is shown; otherwise the login screen is shown.
In a View Controller I created a itemBar Logout button which navigates back to the login screen when it is pressed.
I managed to implement the above logic.
The problem happens when I successfully log in then close the app in a simulator and open again.
When I press the Logout Bar item, the app isn't responsive and does not navigate back to the Login screen.
I tried to use the Coordinator pattern without success. Any help is appreciated!
I want to implement admob banner ad and interstitial ad inside same activity in following way:
Banner ad will be always displayed at bottom of activity and when user performs few action (suppose clicks next button) then interstitial is shown.
Is it against policy?
Currently I have two methods in my mind to implement this :
1) before showing interstitial ad load banner ad, them display interstitial. after interstitial is closed display banner ad again.
2) display interstitial ad in activity containg banner ad, without hiding banner ad.
Out of this two ways which one should i prefer?
Will it be against policy?
There is no problem in displaying banner ads as well as interstitial ads in the same Activity. Personally I would go with option (2) as it is simpler.
I have an app which has a functionality such that when a certain button is pressed, an alert view pops up asking for certain login credentials. When submitted, a web is called which returns that latitude and longitude which are then plotted on the mapview. In case the lat and long are not available, the user sees an alert. Till this stage all goes well. But when I press the cancel button on the second alert the iphone screen fluctuates. After that whenever I navigate to any other page, the screen fluctuates. When the sent to background and then brought to foreground again, it starts working fine. what can be the problem?
In my App, I display and iAd but I was hoping for clarification on a few things:
1) If I display an Ad, it does not look like it will 'automagically' go away, so am I correct that it is my responsibility to dismiss it?
2) I thought I read somewhere that it must stay for a min. 30 seconds. Is that correct?
3) Is it wrong to leave it there forever and let the user dismiss it?
Thanks for the help.
1) If I display an Ad, it does not
look like it will 'automagically' go
away, so am I correct that it is my
responsibility to dismiss it?
Are you talking about a banner or the full screen ad? The banner ad is either updated with a new ad after 30 seconds, or if there is no ad, then the banner view is to be hidden. You are never supposed to show the banner view if there is no ad to be displayed. To learn how to hide the banner view, code samples are in the developer docs. There have also been many topics about this on this site.
You are not supposed to dismiss an iAd. If the full screen ad is being shown, the user dismisses it. There is a delegate callback to handle this.
2) I thought I read somewhere that it
must stay for a min. 30 seconds. Is
that correct?
I've never heard this, but read the above. It will stay for 30 seconds on it's own, no need to dismiss it. If the user is changing views to a view that has no iAd, then you don't need to do anything. But, there is a way to have the banner show on each view. To do that, see the 'iAdSuite' project at developer.apple.com
3) Is it wrong to leave it there forever and let the user dismiss it?
This is exactly what you should be doing (while there is an ad to be displayed). I really encourage you to read the iAd Programming Guide found here.
Hope this helps.
This is kind of on the back of a previous question. Im currently throwing together a simple social networking iphone. For my question you can think of the application to be quite similar to the facebook iphone app.
It is based off the navigation template and the menu view is the top level view controller for my navigation controller. The user needs to log in to use the application.
Im just wondering whether the navigation controller should be the starting view and if the user has not logged in (when the user logs in I will store the login information so that they do not have to login next time the open the app) than it will throw the login page up modally. Or if the login page should be the startup view and on login the login control will create and go to the navigation control.
Thanks in advance
If the user needs to log in before using the application, then showing the login screen modally is probably the best bet for the first view that gets displayed.
Apple does this with their iTunes Connect app that is available when you go to view your sales data. They show a black screen while the app is loading, modally display the login screen, then dismiss the view to show the guts of the app.
Plus in your case it would be nice to have the navigation controller ready in the background by the time the user login screen gets dismissed (i.e. you could delay it with an activity indicator while readying the view). It would give the impression of a more responsive app