I'm trying to use a very simple media query, but looks like I'm missing something. My code seems to work in most clients, but when testing in litmus, from and above Android 5.1 I see that my media query is ignored.
I tried to make the most basic example, which can be found here: https://litmus.com/builder/b46c315
Any idea what I might be doing wrong, or how else to achieve to target these android devices with specific styles?
Android stopped supporting media queries after version 4.4.
If you are testing in litmus you will notice that media queries dont work in android 5.1 and 6.0
This caused all kinds of problems for me and I have now switched to a Hybrid template base for html emails that react responsively without the use of media queries.
The Android device on Android (not 4.4) is gmail app. Google has stopped shipping Android with its own email client and made Gmail App as the default app.
To test on Android you can use Outlook.com app but i has limited functionality compared to Android's original app or iOS.
Related
Capacitor allows us to code once then generate web, Android and iOS applications. Most people using Capacitor will generate native Android and iOS applications.
But strange enough, I can't find any documentation about how to create automated-tests for the two native applications. I can easily test the web application using protractor, jasmine or whatever. But when it comes to native apps, I can't hardly rely on native tooling (Android Studio and XCode) as there are other issues preventing me from testing it easily (ex: no possibility to set Accessibility ID through the views markup, etc).
Where are we at with Capacitor native apps automated-tests ?
I believe this is what you are looking for Ionic/capacitor Integrations for Testing
As far as the community/forums and official docs go there are only 3 ways you can test your apks
Native [Andriod Studio / Xcode] [Emulated versions]
Real Devices
3rd party Integration listed in the link above..
Even on google there very less info on this topic.. most of the blogs/ articles only say that Ionic/Capacitors can be tested just like a normal WEB App
I'm really keen to develop a web browser application for Android Wear devices. To make such application I need a WebView object, but the major problem is that Google has made the android.webkit API unavailable in that OS.
Since Android is open-source, is it technically possible to manually include the needed libraries, by coping them from the android source code on GitHub into my project? Are they going to work like as in a normal Android device, and is it legal?
Here is the link to the API I'd like to use.
Developing a browser based on WebView is not a good idea anyway. Although historically Android Browser was based on WebView, it had to use a lot of hidden APIs in order to work. All more or less functional browser apps based on WebView have to do the same, which makes them fragile. Also, the resulting browser app will not be as secure as a real multi-process web browser.
A better idea is to take Chromium and build it using Wear SDK. And there is already one built this way.
You don't have access to a complete source for Android Wear to build a complete image.
We will develop an app that we would like to distribute in through the following channels:
Android and iOS apps through Google Play and iTunes (the app will
use notifications extensively and presence in Google Play and App store is required)
Web app to run in web browsers on mobile devices
Web app to run in web browsers on laptop and desktop computers. We would like to support Chrome, Internet Explorer (starting from IE9),
Firefox and Safari browsers.
Our understanding is that Ionic is developed targeting primarily 1. and that the web apps in 2. and 3. above are not really what Ionic is intended for. We have looked around to try to understand if Ionic likely works for 2. and 3. and also made some quick tests ourselves.
From one of the links at the end: "Your webapp will run in desktop browsers yes, as it is made of html, css and javascript. The phonegap specific javascript calls (accelerometer, compass, file, etc) won't. Basically, if you stick to standard yes you will be able to port relatively easily your app to most browser, the job at this point being mostly a work of theming."
From another one: "I do know that FireFox is simply not supported. I don't know how well Ionic works in IE X."
To try it out we have built a limited version of our app in Ionic. From what we can see the app works for 1, 2 and 3. For example, it runs without issues on FireFox that is mentioned as not supported in the quote above. This means that to us it looks like the first quote saying that the web app will work in desktop browsers is correct.
I understand that this is a fairly generic question and might be hard to answer, but since we have found contradicting information when looking we are trying to understand more before making a decision.
Any feedback would be appreciated.
Thanks,
Markus
Is it a good idea to use ionic to build mobile web version of a website?
Can Ionic Framework run in desktop web browser like Chrome, Mozilla, IE9+?
http://forum.ionicframework.com/t/ionic-components-on-ie/1826
Phonegap web app in regular desktop browsers
http://ionicframework.com/docs/overview/#css-sass
Ionic is tested for mobile only. Internet Explorer for example is not tested and does not properly handle a number of features in Ionic. Desktop browsers act differently than mobile browsers.
Ionic is focused on building native/hybrid mobile apps rather than
mobile websites.
As such, our browser support tends to be whatever Web View API is
available to native apps on a given platform. For Ionic 1.1.0
"xenon-xerus", that means UIWebView for iOS 7+, and Android 4.1 and
up. Windows Phone and FirefoxOS support is on our roadmap.
If it's cheaper for you to test everything on all different desktop browsers than to develop a version for it sharing the same controllers and services --- go ahead but it won't come "out of the box".
Also, I recommend looking at Electron to build desktop apps from webapps.
ionic is targting mobile apps only , but you can develop your desktop app using node webkit and angular material for example and share some code between your apps
what could be the reason for that, that gwt mobile apps doesnt really work on mobile phone?
iam using a ZTE-Blade Android 2.1 (in germany Base Lutea) mobile phone and i have big problems with gwt-mobile-apps while using this mobile phone.
the gwt-apps are running but there is no reaction when i touch UI like buttons or something.
i must press the button maybe over 100 times to get a reaction.
and that is the case for every gwt mobile app.
Nearly no reaction from UIs like buttons for every gwt-mobile-app.
I wrote a little app in gwt and on the browser on my PC, it works perfect but on my mobile not really.
with other apps like android or jquery-apps, there are no problems.
everything works fine but with gwt-mobile-apps there are no reactions by touching UIs like buttons.
What could be the reason for that?
i really have no idea.
does somebody know this problem and are there similar problems for gwt-mobile-apps on other devices?
i had the same problem on my 2.1 android phone and the only problem is that android 2.1 is to old.
gwtmobile works very nice on younger android devices.
If you look when the developers made the last updates to this framework it shows that they haven't updated it since April 2010.
http://code.google.com/p/gwt-mobile-webkit/
Because of the deversity of mobile devices and browsers it hard to optimze javascript for every type of browser.
You should use a framework which is up to date like jQuery mobile or Sencha Touch 2. They are well focused on this topic.
http://jquerymobile.com/
http://www.sencha.com/products/touch/
Statement of sencha:
"A note about Android support: Due to the overwhelming diversity of physical Android devices on the market, we can only test so many. This support matrix is not intended to be exhaustive, but to give you an idea of the support for Android devices. Your mileage may vary." (http://www.sencha.com/products/touch/features/)
Take a look at m-gwt: http://www.m-gwt.com
This is a mobile library for GWT, that works very nicely.
It uses core GWT concepts (rebinding, clientbundles, ...).
I'm trying to 'mobilize' a site I'm working on using media queries in CSS.
I have an Android phone myself so have been testing on that with good results.
I now want to test on the iPhone but don't have a device, having searched the net and downloaded a few recommended simulators it seems they don't recognise the media queries, but without a device to test on I can;t e sure if my queries don't work - or if its the emulator that doesn't recognise them.
Does anyone know of a emulator for iPhone / iPad that runs on Windows and recognises media queries?
Mike
You should try using ProtoFluid - it's a web app that allows you to emulate an array of mobile devices and tablets, fully recognising media queries.
It's free to use (for now at least).