top | item 41368786 (no title) tonsky | 1 year ago It’s a tradeoff. You either make your app native but only for one platform, or you make it look “universal” and run on all three. discuss order hn newest layer8|1 year ago That’s not accurate, there are cross-platform toolkits that achieve at least a close-to-native look&feel. This is very different from giving up on it entirely and going web-style UI. tonsky|1 year ago If they use native widgets, they usually look really bad If they just “imitate” look and feel, they usually fall very short of the real thingEither way, it’s bad experience for the end user load replies (1) kaba0|1 year ago Do you mean the state of the art java AWT and/or Eclipse toolkit?
layer8|1 year ago That’s not accurate, there are cross-platform toolkits that achieve at least a close-to-native look&feel. This is very different from giving up on it entirely and going web-style UI. tonsky|1 year ago If they use native widgets, they usually look really bad If they just “imitate” look and feel, they usually fall very short of the real thingEither way, it’s bad experience for the end user load replies (1) kaba0|1 year ago Do you mean the state of the art java AWT and/or Eclipse toolkit?
tonsky|1 year ago If they use native widgets, they usually look really bad If they just “imitate” look and feel, they usually fall very short of the real thingEither way, it’s bad experience for the end user load replies (1)
layer8|1 year ago
tonsky|1 year ago
Either way, it’s bad experience for the end user
kaba0|1 year ago