-
All-in-one prototyping tool
-
WebHi-fi prototypes for Websites & Web Apps
-
MobileCreate lifelike iOS & Android prototypes
-
Collaborative prototyping
-
CollaborationShare and get feedback
-
RequirementsRequirements management
-
IntegrationsSketch, JIRA and more
Addendum: Downloaded, installed and registered JIM 6.0. Resaved my files and uploaded them again, with no benefit on iOS devices. So this is probably related to the usernote UI update that was made this week. I would rather have working prototypes than a shiny UI with non-working prototypes.
Hi,
Can you try downloading the iOS app named Justinmind and try to simulate on device using the app?
Click on view on device in prototyper and follow the intructions that will appear.
Please let me know if the scroll issue persists.
Best,
Marc
The iOS keyboard that your app presents does not have an underscore "_" character, and I therefore cannot log in because my email has an underscore in it. In addition, a justinmind account should not be required (by the app) for public users to view a prototype that is not password protected, as that defeats the ability to view a prototype without a password challenge. Your app is not a viable solution until both of these issues are addressed.
Hi Vasken,
The iOS keybord uses the native keybord so by clicking on the button at the bottom left the underscore shuold appear. If this isn't your case you can always copy and paste your email address.
Can you let me know if ou are using any personalized keyboard or in which language the keyboard is set?
For users who don't have a usernote account, they have to click on "Don'a have a password?" and introduce the 6 character token sent in the email that invites them to be reviewers of the prototype.
I hope this helps.
Best,
Marc
Yes, the "_" underscore is now appearing on the keyboards, so if you guys changed anything on your end then it worked, thanks.
I don't want viewers of the prototype to have reviewer capabilities, so granting them reviewer status and generating a 6 character token (and cluttering their UI with yet another downloaded app) are all out of the question in terms of fixing the new bug that causes screens to be cut off on iOS mobile devices. Could you please address the bug and why you are not fixing it?
Also, I was finally able to log in to the app on an iPad, tried the prototype and... yup! All pages are still cut off at the fold line so users cannot scroll down. This is true whether in portrait or landscape orientation (it actually cuts off at a different spot depending upon where the fold line is). So all iOS prototypes are still not working on mobile devices.
Vasken,
Can you send screenshots of what you are seeing?
If it is possible, can you send the .vp file of the prototype that is showing cut off to jim dot support at justinmind dot com?
And I don't get what the "fold line" is; could you elaborate on that?
Best,
Marc
The "fold line" is the bottom of the device screen, beyond which you can no longer see the page without scrolling. This line is at a different location on the page when the device is in landscape or portrait orientation because the amount of vertical screen real estate is different. Your changes to the iOS code is causing prototype pages to be cut off at the fold line (e.g. if you try to scroll down then nothing beyond that point exists).
I will send screenshots and .vp file to the address you indicated, but really, you should be able to see this yourself.
Hi Vasken,
Please click again on "View on device" in prototyper and refresh the prototype in your devices and the scroll problem should be solved.
If you encounter any other bugs please let us know.
Best,
Marc
This has fixed the 'clipped off pages' issue but introduced others. Now when I click a link that is well down the page, the new page does not load at the top of the page, but rather at the previous page position. For example, if I scroll 1000 pixels down a page and then select a link, the new page loads already scrolled 1000 pixels down the page. Also, page scrolling is now choppy instead of smooth, but this is a lesser issue.
It looks like you did not fix the iOS page clipping issue but rather replaced the iOS code with the Android code, because I used to see these two other issues whenever I ran an Android prototype on an iOS device. I will have to leave this Problem open and start a new one regarding the page position error.
Hi Vasken,
There is an update planned for september where the issues above will be adressed.
Until then, unfortunately, you will have to use a workaround:
Draw a dynamic panel, make it larger than the screen in the direction you want the screen to be scrollable. Then when everything is drawn, all the items in place... make the panel the same size as the screen and remember to enable the scrollbars for the dynamic panel.
Sorry for the inconvenience this may cause.
Best,
Marc
Comments have been locked on this page!