Slow stuff on old devices

[dieulot]

Slow stuff on old devices

[nolimits4web]

Wow, thanks!:)

Swipe back

The most performant problem here is because of animating box-shadow on "right" page. Now it is possible to disable it by passing appropriate parameter. I may force to disable it on iOS 6, but think it is better to give opportunity to user to decide should he disable it or enable

Slider

This part is really fun, because it is actually 100% default input:range with no single line of JavaScript:) Don't event know what can be done here

Swipe to delete

I think that now i will add fallback option to simply open/close it with simple swipe without smoothing move below finger/mouse

Pull to refresh

That is the problem, yes. Because as you note, first pulls are made by setting translate on page container while native scroll unavailable. Need to think here...

Form inputs

Yep, i will not merge FastClick lib into Framework7. It has own similar system. As you see it is already ok for any links and buttons. Just need to improve it for inputs

Switch

That is probably unfixable problem:) Switch is made with single input:checkbox element, and unfortunately iOS 6 doesn't support animation/transition on pseudo elements like :after, :before

Scroll

Yes, problem exist, it is because live event handlers, already work on improvements

[sidneys]

The iPhone 3GS is a 5 year old device - most iPhone users today are running iOS7 on at least an iPhone 4, most are on 4S or 5. Also, iOS7 is available only for Retina Devices (iPhone 4+). Please do not waste energy in the "Rat Race" trying to support old/deprecated devices (this is also the approach Ionic is using very effectively, as they just secured 1m $ in funding)

Please focus on developing new, heavily required features which are currently holding back widespread adoption of Framework7, such as out-of-the-box, perfect integration with AngularJS and / or Cordova.

[yoorek]

@sidneys +1 Yes! Absolutely!

[dieulot]

I too think the 3GS shouldn’t be bothered with. I think iPhone 4 and up should though.

Here are some stats: http://david-smith.org/iosversionstats/#iphonebreakdown

Non-retina screens must unfortunately be taken into account because of iPads, half of them aren’t retina.

Another interesting tidbits I got from those stats (mirrored by Apple’s App Store stats https://developer.apple.com/support/appstore/) is that iOS 6 isn’t used much anymore. At last year’s WWDC Tim Cook showed iOS 6 at 93%, this year at pretty much the same time iOS 7 is at 88%.

I haven’t looked much into how Framework7 works actually (just got excited by the demo), so I’m not making any suggestion as to what is most pressing for the framework.

[nolimits4web]

Guys, don't worry:) No one trying to make it compatible with all devices. But it is also good to understand why it works slow on some old devices OS, because some improvements for old devices also improve overall framework performance ;)

[nolimits4web]

I think we may close it for now

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.