How do WeChat display a system loading screen like this?
When I first launch the app, it's showing me the second image. Not like WeChat.
When I try to do it, it's different. My one is showing time as well. I'd like to hide Title and time from status bar and show title under the activity indicator while initial loading i.e. show a loading screen like WeChat.
There isn't an API for controlling the visibility of the status bar in WatchKit. So you cannot do that.
About splash screen:
Firstly to the splash screen, no, just no. Splash screens are only
just about acceptable on phones and tablets, but the Apple Watch is
used in a very different way. The way we look at usage between the
Apple Watch and phones and tablets, is that a user will be using the
watch for a brief moment, 5–10 seconds and they are out of there! If
we put a splash screen on the Apple Watch, users will become
frustrated that they have to wait 2 seconds, just to see some quick
information. On other devices it’s not so bad as the user’s behaviour
is more likely to be relaxed and willing to give a little more time to
viewing the app.
Related
I am making a simple iOS application with two Views using gluon. In one of the views I need to be able to keep screen alive indefinitely, prevent it from rotating and have it full screen without the status bar showing. The other View should have the default behaviour(rotating normally, let screen go off when there is no touch input by the user and status bar should be showing).
I have seen some tutorials on how to do this on Android binding an interface to native code. Is this possible to do in iOS? I have looked around everywhere online and no one seems to have done this. Any pointers ? Thank you.
We are currently checking if our app is compatible with the upcoming iPhone X and its new form factor and gestures.
We noticed a problem regarding the switch to home screen gesture where swiping up actually triggers the action on the buttons located at the bottom of the screen.
In our case, this is problematic, because our app is a remote controller for very high end amplifiers and the buttons located at the bottom of the screen are volume buttons..
See image:
Anyone here had to deal with this kind of issue lately?
I was thinking of some kind of event that could be triggered by the swipe up gesture and disabling the buttons maybe?
Thanks for your help.
So we finally decided to go for the safe area principle and stick our bottom bar to the bottom of the safe area as suggested by Apple.
It's a bit annoying as it adds a big empty space at the bottom of the screen but I guess every app having actions there will have the same problem (tab bar for example)
Here's the article I used:
https://useyourloaf.com/blog/safe-area-layout-guide/
If you found another solution, I would be happy to read about it.
Thanks.
Somewhere in the near future, an application I'm working on is going to its own pass to be stored in the user's passbook.
Since you cannot really test the passbook app from the watch in the simulator, and my watch will be arriving next month, I was hoping someone could shed some light..
I had a few questions about passbook for the apple watch..
Is it safe to assume the passes in passbook will automatically be
synced and added from the phone to the watch?
Are there any sort of visual guidelines when it comes to showing
passes on the apple watch? Does text automatically shrink? are things truncated? Are only certain fields appearing on the watch to conserve space?
Is it safe to assume if the user turns their wrist, the screen will
not shut off if a pass is currently being displayed?
Yes it automatically syncs.
Thus far I've noticed that the Pass is added to Apple Watch Passbook quite quickly after added in iPhone; although if you reorder the passes on the iPhone the order takes a little longer to sync on the Apple Watch view. (I haven't timed this under different scenarios but I'll test that and get back to you). Please note, I have >300 passes in Passbook so a 'typical consumer' may not experience the same.
Visual Guidelines.
The logo image remains at the top left of the Watch view of the Pass and automatically scales.
The strip or thumbnail image are removed from the Watch view. A background image (on an event ticket type) remains visible but is not scaled.
The header fields moves below the logo image (i.e. it is not to the right of the logo as it appears in the phone).
All other (text) fields appear on the watch view, but they are not side by side. The are presented in a 'list view' - separated by a fine line between each field. I have experienced some situations where the text length runs over one line (e.g. an email address i.e. no spaces between words) and it doesn't look so beautiful as the text does not resize to fit all on one line.
The pass automatically scales width-wise so it fits in the watch view but it is "longer" than the watch screen so you scroll the Pass up and down.
The pass length in the Watch app is dependent on the number of fields used in the Pass.
As you scroll to the QR code and tap on it, all other background colours and the 'close' link disappears and only the barcode is displayed. The square barcodes look significantly better. Of course redemption/scanning still works with the PDF417 barcode but it just doesn't look as nice in the watch view. It is presented in vertical format in the centre of the watch view, with black to the left and right of the PDF417 barcode.
Please note that there is no 'back view' on the apple watch pass. i.e. you cannot flip the pass to access the back of the pass as you can on the iPhone.
Screen shut off
The screen will not shut off only if the barcode has been selected (as described above). If you are just viewing the pass and have not selected the barcode the watch screen will shut off after time of no activity or if you turn your wrist.
If the barcode is selected, the barcode remains on the screen irrespective of wrist position and does not shut off over time.
Other - Lockscreen notifications / convenience.
Works the same as iPhone when in proximity to an associated GPS location or beacon or following a push update.
The pass can be accessed by tapping on the notification (i.e. no need to open the Passbook app on the watch) and can also be accessed by a swipe down to notifications. A 'small pass' is displayed in notifications. The 'small pass' is the same width as the watch face, and about half the height (same as other notifications). It consists of the logo image, inherits the background colour of the Pass, and includes the pass description field (when in proximity) or the updated field (when pushing an update).
Is it possible to hide splash screen in MAF app and directly display some form/page to gather information from user at place of splash screen, and while user is being entering his values then initial loading process (which loads behind splash screen) can be continue at back-end?
The splash screen is of value to you as users know you app is loading. Its purpose is to load quickly as the rest of the app sets up.
Why would you want to move logic into this visual process? I want to caution you that I think it's a poor choice to reject industry standards. Work with the framework.
I am building a project. Everything fine. Then I installed that on my iPhone.
My iPhone stack at the front screen and that's it.
Pressing the power off button for long doesn't work.
The xcode says Could not launch "Application Name". permission denied.
Should I just wait till iPhone run out of battery?
Try to restart iPhone using the instructions here:
http://www.apple.com/support/iphone/assistant/phone/#section_1
"To reset iPhone, press and hold the Sleep/Wake button and the Home button at the same time for at least 10 seconds, until the Apple logo appears."
My iPhone5's display became so large that I could not use it. When I tried to reset the size just like I do on my MacPro, it didn't work. So, I thought I'd restart it, but when I pressed the top button, the screen with the "slide to power off" came on and it was not possible to complete the task. It was frustrating and I thought of taking the battery out and putting it in again, but then I thought to try sliding the bar with my stylus pen and it worked immediately.