![]() ![]() Something I need to look into definitely.Ģ. The bug in your first screenshot is completely my fault and not the frameworks. I appreciate the feedback, always take that onboard.ġ. Obviously the majority of users don't notice this stuff, but I just don't think you can make the claims you do about Phonegap.įor new apps these days, if you have to go the hybrid app route, I don't see how someone would justify choosing Phonegap over React Native. This isn't your fault, but it's very hard, if not impossible, to get all this stuff 100% correct compared to a native version. It's also quite easy to screw up the views with multitouch pinching (which users will notice when they try to interact with your map): The drawer that comes into view from the right (city detail?) also doesn't scroll at 60 FPS and actually prevents the last row of details from showing on the screen unless I drag it into view (at which point it will snap back down when I release): I don't know if the map is ever supposed to be displayed in a tiny portion of the app at the bottom, but here is what it looked like after some quick button presses:Īdditionally, the drawer list items don't scroll at 60FPS, and the scrolling acceleration is different from android's native acceleration. I just downloaded your app on my Nexus 5 and easily broke the UI with just a bit of button pressing. However, I disagree with with "Phonegap has great scrolling, touch events work as they should and UI quirks are not a fault of the framework" If it gets users and the users are happy, then you've succeeded. ![]()
0 Comments
Leave a Reply. |