Is anyone familiar with a comprehensive list of mobile devices and their browser's cache limits for images?
I found one reference for iPhone:
http://www.niallkennedy.com/blog/2008/02/iphone-cache-performance.html
But it's 3 years old. It does state, however, that the iPhone won't cache images over 25k.
I'd like to know if that's still true and if anyone has similar info for Nokia, BlackBerry and Android devices.
The only posts I could figure out (by searching on Google) are the following:
Mobile Browser Cache Limits: Android, iOS, and webOS
Mobile Browser Cache Limits, Revisited
How Mobile Browser Cache Affects Browsing on iOS, Android, and More
Related
I have a very big problem and unfortunately I cannot find a solution. Help from some professionals would be really great. Thanks!
The little problem
I have a Angular Web App / Android App using Cordova. My app needs at least the Chrome Engine 50 to support all functions and looks right. Unfortunately I noticed that there are many devices that use a much older version. Also the devices do not use a common source for the Chrome Engine. Some use the Chrome Browser itself or the Android System WebView. In these two cases I can tell my testers, install the two things and then it works. Currently I check at the start of the app which version is installed and if it is less than 50 I show an info that users have to update ther apps / components particularly important here the two things (Chrome Browser itself or the Android System WebView). I rather say my users that they should update all ther apps because some hardware manufacturers have their own apps that include the Chrome Engine. That alone I find very unpleasant.
The biger problem
But it is worse with devices that have their own Chrome Engine built into the firmware. So one that you can not update at all via the apps update only just the hardware manufacturer of the phone can update them with firmware updates. So many cheap devices that don't get any more updates simply fall out and bring me possibly bad ratings.
What can you do?
Maybe someone has an idea? Because this way I can put my app in the store from Android 4.4 on but even 6.0 devices have older Chrome Engine versions in their firmwares. Can't I provide a chrome engine version or say I use it there from Chrome or from the Android system WebView? I'm really on the edge and need a clever solution.
I would be very happy about some help or exchange. Thanks a lot.
Best regards
Robi
I have few SSRS reports (with charts, gauges etc) deployed to the server and they all work fine but not so well when viewed as well worked upon on cell phones/tablets.
The users find difficult to choose the report parameters, selecting from drop downs and also presentation of data through charts, gauges etc.
I am thinking to modify the SSRS report for cell phones but not sure how to progress. I have searched and started reading some blogs but thought of asking suggestions of experts here who may already dealt this.
I have sample RDL files (deployed to the report server) that I can post here but they are any other typical SSRS Reports with various parameters, charts, gauges etc.
Many thanks.
Please share your thoughts.
Looking for an solution for the same problem, I have found this answer. I have applied it ant it worked!
My context is:
I'm using the ReportViewer Webform component:
Microsoft.ReportViewer.WebForms, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
It tested in Androind Asus Zenphone 2. Using the default browser and Chrome.
It worked at desktop chrome too.
The code change:
Replace:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
with the following tag:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
Are the reports being delivered using Report Manager, SharePoint or a ReportViewer control in a web page?
You're using SQL Server 2008 R2, so the only supported browsers are Internet Explorer, Firefox and Safari and although it doesn't explicitly state it this almost certainly refers to the desktop versions of these browsers so there's no guarantee that mobile versions will work the same way.
So the SSRS technology you are using is not designed with modern day mobile devices in mind. That said you can still try to make this work: You need to ensure the users are using either Firefox (on Android) or Safari (on iOS). Note that Chrome (or related browsers) are not supported at all. You need to consider how the report security is going to work (e.g. only Basic authentication is supported with Safari).
In terms of layout and report components, you'll have to do some trial and error testing to see what works - and remember it may not work on all devices. You might want to consider providing links to render the reports as PDF files, which have much better support on most devices. There is a great blog post by Adam Aspin on some layout techniques for reports on mobile devices here: https://www.simple-talk.com/sql/reporting-services/mobile-bi-with-sql-server-reporting-services/
Generally though, if you're trying to design a solution for mobile devices you really want to consider an upgrade to a more recent version of SQL Server which has support for more browsers (including Chrome) and security options.
What is the best way to test my website across various mobile browsers AND various versions of each of those browsers.
Additional Info:
Most of the online cross browser testing support wide range of desktop browser testing, and quite a range of mobile devices. But they don't seem to offer various versions of mobile browsers on those devices.
This similar question is quite old and it is surprising that in spite of the proliferation of mobile devices and focus on responsive designs, testing services for mobile is not catching up.
Major mobile browsers I would like to target : various mobile versions of Safari, Chrome, Firefox, Opera, Dolphin, UC Web etc
Just wanted to note this and this good alternative to online testing services for desktop browsers. Maybe something similar exists for mobile browsers too?
I'll suggest that both Opera's "device mode" is a really good for a first crack. But nothing beats actual device testing. I have found the odd case where Chrome's iPhone mode renders something different than what the actual phone does, but I would say it is about 90%. And the fact that it is so much easier to tweak code, and refresh using Chrome on the desktop rather than tweak, and refresh on phone, that I tolerate the 10% difference as long as I can. Then I just verify on an actual device after I am done with Chome's device mode.
I have not used Opera's device mode, but have heard it is good too.
There is a tool called as https://www.browserling.com/ which can be used for Desktop and Mobile testing(Android)
I don't think there is one way of doing cross browser testing across various mobile browsers and versions. It all boils down to what you want to do?
It is impossible to cover ALL browser combinations and versions. So my suggestion based on experience would be-
If you have too many combinations in mind, use a combinatorial tool (pairwise testing) from here - http://www.pairwise.org/tools.asp and reduce the number of permutations to get the best coverage.
Then go to Android and Apple website to see what the most commonly used phones and versions in the US, Europe and Asia region are based on where your customers are located. They have all these stats publicly available on their website
If you have google analytics see what browsers, versions and phones your users most commonly use to access your website
Now, you will have a list of devices and browser versions which is more focused.
Check what budget you have to invest in cross browser testing. Based on that I would recommend buying at least a couple of phones and tablets based on the usage statistics you got in the first 3 steps. Then, you can choose from a number of cross browser testing tools/services like
BrowserStack
Amazon Devices Farm
Saucelabs
Now atleast you have a more scientific way of doing cross browser testing :-)
I have to develop a web app that could be used both online and offline on iOS7, iOS8 and Android. The app has a lot of contents and images, because it is a brochure app with more than 300 products, each one with image gallery. That's why I'm scared that the device is not able to fully cache the whole application.
Online I can only find infos related to iOS5 (cache size = 5MB) but nothing more updated than this:now we have iOS8 so maybe the cache size limits have been increased...
Maximum appcache size for android devices is limited to 5 MB. But i could not found issue in apple products such as iPhone, iPad, iPod..
I've an android app already developed.
The android app is essentially a wrapper around a HTML5 web app.
We use HTML5 offline caching to provide the ability to play when disconnected from the internet.
Chrome/Firefox on the desktop will cache the video and images however Android devices
appear to selectively ignore video in the cache manifest which prevents the video from
being stored locally on the device.
It's understandable that Android would ignore caching video to keep the storage use to a
minimum on mobile devices but we need a way around this.
Just stumbled across this question after I stumbled across an answer - so thought i'd help out!
I'm trying to do a similar thing for Android/iOS, and as far as I know the appcache is very restricted on mobile devices (Android varies depending on available disk space & browser used, and on iOS I haven't had luck getting above 50mb).
I recommend using a framework such as PhoneGap or Chrome Apps - they offer other forms of local storage by communicating with the device's native file APIs.