I'm currently hiding the address bar on iOS using the standard scrollTo technique (something like this). I am also using an iOS 6 smart app banner, but when using the above technique to hide the address bar the smart app banner is also hidden up by the address bar off the top of the screen.
Is there any way to hide the address bar but not the smart banner?
Long story short, the clever folks at HTML5 Boilerplate have already solved the problem in their mobile version.
Check out MBP.hideUrlBarOnLoad in helper.js, which hides the address bar and doesn't hide the smart app banner. It appears that the key difference is probably MBP.getScrollTop, which gets a more intelligent scrolling point than simply scrolling to 1.
Related
I have this app that has a bar at the top of the page that has a bunch of clickable elements it has always been a problem since on Safari IOS when clicking high up it brings down the address bar and exits fullscreen. We solved this initially by adding some padding up top to make the clickable area larger but they seem to have increased this size on IOS 13 and adding more padding will make it look horrible. Anyone had this problem and have a workaround for it?
Some way the click area for bringing down the address bar smaller or something?
The big problem is that we need our app to stay in fullscreen so the most optimal would be to be able o decrease the clickable area for the address bar to come down or to be able to block it in landscape mode is there really no way to go around this? for instance going into twitch.com on safari and iPhone and put it in landscape you are not able to press the search icon.
I have the same issue, I don't think is possible to fix this as it seems to be a safari issue, if you check not event apple.com site works as expected.
The workaround I did is detecting when the app gets out of fullscreen by comparing the screen.height with the screen.availHeight and move the top bar just below the address bar and there users can click, not optimal, but works for us. :)
Hope it helps
In your CSS code try to remove every value of "REM" "VW" "VH" use only pixels "PX". that should fix the issue 100%.
iOS has a feature that (I'm using both iOS 10 and 11) when you use a location-based app, say Waze, and you put that app on the background, there will be a blue navigation bar with a blue status bar background saying that Waze is currently using your location. Then open up your own project and close the Waze, this will happen.
Any idea how to fix this one? I'm guessing some configuration in the AppDelegate. Something to setup upon making your project active. I've tried the same steps in my other project and I have no idea why does that other project handle it a little better. The other project has a readable status bar but different background color, still quite a mess but better than in this project in the photo.
This is how your app should work:
The status bar is transparent.
Your view controller's main view should underlap the status bar; it should be fullscreen.
Your views should use autolayout to respond to changes in the size of the top bars (they should be pinned to the top layout guide or, in iOS 11, the top of the safe area).
You are not doing that correctly, so your app does not behave correctly when the status bar size changes due to the location manager bar. You probably have the same problem with phone calls coming in. You can easily test in the Simulator by choosing Toggle In-Call Status Bar.
I am just starting out iOS development and have some doubts about Tab Bars Human Interface Guidelines provided by Apple.
On the iOS HIG document concerning Tab Bars, it reads:
"A tab bar appears at the bottom edge of the screen and should be
accessible from every location in the app."
The app I am developing and would like to see published in the App Store once finished, would have a ListView as it's first screen that would then go to another screen with a tabbed interface after an item being selected. It would also be possible to go back to the first screen (the one with the list) at any time within the tabbed interface (the 2nd screen).
So, my question is if it's ok to have a Tab Bar interface only in the second screen of an iOS application or would something like that might result in some restrictions by apple approving?
Thanks.
Short answer is YES.
Yes, you can have tab bar in second screen. Consider the app where you have first screen as language select screen and second screen with tab bar controller.
With statement below, what Apple means is once you are in tab-bar controller and tab-bar controller is in scope, tab-bar controller should be accessible. You can hide the tab-bar, but on tapping, it should come again at the bottom of screen.
"A tab bar appears at the bottom edge of the screen and should be accessible from every location in the app."
Main words -> Should be. Apple wants you to make your apps in the most intuitive and user friendly way possible. Many standard apps use this paradigm (ie App Store Application) so they know iOS users are accustomed as to how to navigate. However, Apple themselves even make exceptions to this rule (ie. Playing a song inside the Music App). But yeah, they'll let you do it no problem.
I have been developing hybrid apps on iOS and the most glaring problem I am having is the back button that emulates the native back button on the top navbar has a much smaller area.
This may be due to the button being on the edge of the top edge of the screen and the webview doesn't interpret taps on the edge to be intended for the webview, maybe the status bar.
I have even enlarged the padding on the button element to the point where it takes up the whole top left corner of the screen and wont register a tap unless you aiming for 3.5mm beneath the top of the webview. On a native app you can aim 0mm away from the edge and it registers.
This may not seem that bad, however when you allow a long term iOS user that 3.5mm is very apparent, and their mental model of where a touch should register makes them immediately think the app is broken, instead of them tapping the wrong area.
I am interested in any other information regarding ways to minimize this discrepancy between native and hybrid, or proposed solutions/information leading to a better understanding on why this occurs.
Using Cordova / PhoneGap and Kendo Mobile to implement the app
I am facing problem in my app because of the new split keyboard option in iOS5.
Is there any way we can hide or disable this option in objective C?.
Thanks in advance.
Seems like the split keyboard does not use the same functions as regular keyboard. see here.
missing kb notifications
Here's the problem: You can iterate through the keyboard subviews and hide the button but you can't control the state of the keyboard when going from one app to the next. It would get really tricky and sneaky to force the private api to call when the application did enter foreground and the keyboard became active.
You could do this but apple may deny you from the store.
Fix your view to account for the keyboard movement. Your users will dock or unsplit the keyboard when there's clear disruption in the UI due to the keyboard placement.
Other solutions could be to move the entire view that requires keyboard placement to be docked or undocked using the notifications. See other posting here: StackOverflow article