Recent Comments

Comment RSS

Removing size limit of a page

Tuesday, 04/06/2010, 05:46 AM by admin

From the first version of MobileNoter there was a limit on a maximum size of a page that MobileNoter can transfer to iPhone. MobileNoter was not able to work with pages larger than 5 Mb. This included text on OneNote page and images, and not included attachments. There is also option to resize images in Windows Sync Client, so it is quite easy to fit the page into this limit.

For most of the users this was acceptable, based on a feedback. Although for some scenarios 5Mb is not enough. When you have a long page with many images (not printouts with pure text, but images from camera, for example) the page may exceed this limit.

I hate to say this, but nevertheless, there was an option to redesign notebooks by splitting pages. This might work for someone who had critical need to have some notebook on iPhone. Again, we do not think that this is ok to force user to change notebooks only to make them compatible with MobileNoter and sorry for inconvenience.

Why we had this limitation:

  • Data transfer and iPhone data storage were not optimized to work with large pages. This is purely MobileNoter issue that we have fixed in the 1.3 version.
  • We use Safari to render OneNote pages on iPhone and it has some limitations too. First of all, there is limitation on an individual image size. Also, when there are too many images on a page (how many is depends on a free RAM, I presume), it doesn’t render random images and shows question mark instead. Unfortunately, we can do nothing with this. Completely rewriting MobileNoter not to use Safari is a huge task that we cannot afford in the near future. Good news is that we found a solution how to display missing images for a user, so important information is not lost (see below).

In the version 1.3 we made a giant step to overcome this limitation and we hope it will work for most who suffered from 5Mb limit. But it is not as good as we wanted it to be, so we are not going to stop on this and will try to find other solutions. For instance, we have an idea of splitting large pages in parts, so they are displayed not as one long page on iPhone, but as several.

So, how does it work now?

  1. When transferring some page, we are processing images from the top of a page toward the bottom of it.
  2. If we meet a picture that is larger than Safari can display we resize it to fit Safari limitations (2Mb)
  3. If a sum of size of abortion pill pain already processed images reaches 25Mb, we replace all subsequent images by links. When a user clicks on a link, an image is displayed.

By other words, if there are many images on a page, from some point they may become substituted by links following to a separate page with that image and a back button. The whole page with all images will be on your iPhone, there will not be problem with syncing them and you will be able to access all data.

Please feel free to ask any questions. If you have any problems with large images/pages in 1.3 release, please do not hesitate to contact our support team, we are working hard to develop product that fits your needs and is easy to use.



12/10/2017 6:46:10 PM #

Pingback from

Mobile Safari 5mb HTML5 application cache limit? - QuestionFocus |

Comments are closed