I am in the process of launching a facebook chat bot that is pretty gif heavy and have a couple questions. We are running into load times that are way too slow, especially on mobile. While I know some of the gifs are way too large and need to be cut down, a lot of the smaller ones were also having this problem, so I was curious if you guys had some tips:
What's a good rule of thumb for gif sizes for fb chat bots? Is there a file size that is best not to exceed? We are having the most trouble loading them on a mobile device. What's a good size limit for mobile browsers?
Does facebook load all the gifs on the backend at once, or does it load them as they get called? I ask this because if it's loaded all at once in the beginning, having a lot of gifs in there would be an issue i'm guessing.
Anyways thanks for the tips have a great day!
Related
I need to play some videos in a mobile application. These videos will be created on Camtasia software. The Q I have been asked is that what the dimensions of videos should be during the creation in Camtasia to make sure that videos will be OK for different screen size in mobile application.
It is not the responsive issues in developing I am talking about. No doubt I will take care of these issues as a developer. The Q is What issues need to be considered when videos are creating in Camtasia? I suggested that Height: 1920 and Width:1080 can ensure us that with applying responsive issues in developing time, there won't be a serious problem to display videos on different phones( different screen size).
Thanks for your concern.
Does anyone knows a solution to cache YouTube videos on a chrome app ?
I know there are ways to write data and access it later, but i can't find a way to do it with Youtube.
I'm aiming at be able to display those videos Offline or just to consume a small amount of bandwidth.
Thanks in advance.
I am working on a web-application which has multiple videos sizing upto 22MBs.
The requirement is to cache these videos or store it in local-storage so as to avoid buffering of the videos every-time the end-user hits the website on iPad.
Is it valid to do such thing ?
I need a suggestion to check if this practice is good to use such large amount of memory for video caching in iPad ?
(The application is majorly accessed through the safari on iPad or iOS)
I'm not sure about best practices for video since I haven't done much with video, but if you're looking for information about how much data you can hold and how, check out http://milesmatthias.com/post/21323839252/the-current-state-of-client-side-storage for a summary of the different tactics and their size limits.
I'm building an iPhone app for existing site (a local news site)
Main page with articles headers, when click on them you move to the article page. Simple.
This is the first time I'm building such type of app.
I have 3 general questions, just to make sure :
For the iphone, Do we need to
re-create the website article's
pictures for the iphone ? or there
is some programming tool that on the
fly make the files looks better on
the iphone ? or maybe, there is some
technique that creates one artice
picture that looks right both for
the server and the iphone ?
Usually, Do you need to create
special data channels from the
iPhone webservice ? or programmers
just use the existing rss channels
of the webserver ?
If someone know nice artice about
this stuff, It will help a lot. just
see what other are doing.
thanks.
You can see the intent Media apps, these apps are working like what you want your app to.
1) You're better off creating mobile versions of the images. You can do image processing on the iPhone, but you'll have to have the original and that makes the whole thing pointless (ie. you have to download the whole thing.) Generate a mobile thumbnail when those are uploaded on the server.
2) RSS will do. There's a very good tutorial at cocoadevblog.com about approaching such a task (I guess this covers 75% of the work you have to do)
3) Check 2) ;-)
if your download image is bigger the the thumbnail you are trying to display,
then the problem is in your code that change the image size. check carefully what are you doing to the image after downloading it.
I would recommend to create square thumbnails of your pictures at the server level. This will allow you to easily position in the iPhone screen, plus you will not need to download the whole image from the server.
nnahum
How does the Facebook app go about downloading/displaying the images in photo galleries? They appear to load in at varying times which would indicate some degree of threading? Surely the app doesn't spawn X amount of threads (where X is the number of pictures) as this would cause performance issues? Can anyone enlighten me as I would like to use something similar in my app (I will be regularly downloading a large amount of photos and displaying them in the app so downloading them one after another takes too long). Also, these photos change on a fairly regular basis so downloading once and cacheing isn't really an option.
Is there some kind of framework/solution around that might help me achieve something similar to Facebooks galleries?
Thanks,
Jack
The code the Facebook app uses to do this has been open-sourced as the three20 library. This functionality is provided in TTPhotoViewController.
Have a look at the LazyTableImages example from Apple. The images are downloaded asynchronously and have a reference back to where they are supposed to be displayed.
I would recommend you use this Library, ASIHTTPRequest, which is like an extended version of the NSURLRequest. I have been using it to download images for later display, asynchronously. It has a nice CACHE implementation which saves bandwidth and loading times on your app.