Bundler ubiquity - Chrome or Android 2.2?

Since Chrome/Firefox/IE are gradually deprecating SHA-1 certificate, cfssl bundler needs to adjust the definition of 'ubiquity', which is the default bundling strategy (or BundleFlavor as we call it). We have observed in the wild that some SHA-2 certificate authorities are not trusted by legacy systems like Android 2.2. Fortunately, we usually found a cross-signed SHA-1 certificate that bridges the trust verification to some older trusted root CA shipped with Android 2.2. Chrome will warn user with degraded UI (or just reject the certificate) when seeing such 'augmented' certificate chain. So, sometimes we have to choose between 'Chrome compatibility' or 'Android 2.2 compatibility'.

I am inclined to make 'ubiquity' mean 'Chrome compatibility' that SHA-2 certificate chain are chosen over Android 2.2 support. But I also want to create a new flavor 'legacy' to accommodate legacy platform compatibility. Or we can use a new BundleFlavor 'modern' for 'Chrome compatibility' and keep 'ubiquity' flavor as it is. I hope the community can chime in and tell us what you feel about 'ubiquitous certificate chain'.