Quote:
Originally Posted by bhaak
Yes, that's exactly the point. How much effort will it be to support both devices? We just don't know yet for sure.
For native applications, it's quite likely that there will be no issues on the level of the CPU. Compiled code per se will likely run on both KT and the KP. But what about dynamically linked libraries? This will depend on how similar their firmware is. Then there are different screen resolutions which might or might not screw up your layout.
I think it would be surprising if wafs and kindlets wouldn't work on both devices. After all, browsers apps and Java apps easily work cross-platform and Amazon deliberately breaking compatibility would be strange. Unfortunately that doesn't include patches to the inner workings of the framework like JBPatch.
|
Different DPI and capacitive touchscreen are already supported by current KT's firmware (and
was introduced with 5.1.0 or even earlier). And screenlight
is also supported beginning from 5.1.0 (as had been found by
ixtab).
It's just reasonable to expect that 5.2.0 is updated 5.1.2, KT-specific code (167 DPI, Neonode zForce touchscreen) wasn't removed and choice between KT- and KP-specific code is made in runtime.