4 ms·
I know, it is not the developers at fault , we the devs pushed against this, we tried to get the native input to look as much as possible as the design but it w
by simion314 7y ago
I know, it is not the developers at fault , we the devs pushed against this, we tried to get the native input to look as much as possible as the design but it was not accepted, we had no choice but to use JS and get teh pixel perfect design.
- jonpurdy 7y agoI’ve been in Product Management positions and always advocate for native controls over custom. Too many times I’ve seen custom stuff take way longer to build and make work responsively. Native might not be pixel-perfect to a design but that’s okay; design is how it works, not how it looks.
- matheusmoreira 7y ago> we had no choice but to use JS and get teh pixel perfect design There was another choice: sacrifice the pixel perfect design and accept the native inputs.
- simion314 7y agoBy "we" I mean the developers, we can explain the upsides and downsides of the solutions but we don't decide the look and feel.