With a bit of work I divided the whole project in different screens in a way that each screen would use just one datagrid/datamaster. Now the complex screen I talked about before loaded in the same decent time, so the issue was not having many datamasters, but using serveral datagrids, related to different datamasters in the same screen. I tried then to leave the datamasters, created a new screen and use the datagrids related to those datamasters but in this new screen. When I deleted 2 of those datamasters and datagrids it suddenly loaded in a very decent time. I had 3 datamasters, with not many entries (just 15, 5 and 10 entries respectively). The big issue in my case were the datamasters and datagrids.
So slow that I had to present a popup for the user saying "loading items" which would last about 15 seconds on my iPhone 6.
With time it got really slow every time I (as a user) accessed to this complex screen. In the old web users were use to navigate through independent web pages, nowadays one-page sites are very common so you want all panels state to remain as they are (and even more if it is a prototype of a mobile app).Īnyway, so for all these reasons I used to just have one complex screen and use dynamic panels for everything, dynamic panels are the most awesome feature of JIM in my opinion. This is sometimes convenient, but some other many times not. Every time the user changes from one screen to another, every information on what panels were selected, what was the scroll position in some panels, etc, is lost. I was designing a big iOS prototype, with just a login screen a tutorial screen and then a complex screen containing everything else. I will tell you my experience with my last big prototype and let me know if it helps you figuring out what your cause might be: Hi! I have been dealing with these kind of issues myself every time a prototype gets complex.
0 kommentar(er)
