![]() So today I’ve gone into depth to explore what I can do better here. In my original version of this button I did some basic adjustments to account for this but after living with it for a few weeks I didn’t like the result. The 40mm watch is a really different screen size to the 49mm, so naturally things will need to shift. This is largely just an artifact of the same size text being used here so the relative shape and position of the label will naturally need to be adjusted to look at home on the screen. In some watches the date label is pressed closely to the top margin of the screen, in others it floats down considerably. Pay special attention to the position of the time label for reference. ![]() If you look closely at them you’ll notice that the exact layout of the top areas are actually relatively different between the models. Here is an array of all the different Apple Watch versions that this screen supports. However, placing a UI element on the inside of the top corner of the Apple Watch has lead to a number of really tricky layout challenges. The fast switching button in the top of Pedometer++’s workout view (discussed here) has turned out be a really great solution for providing persistent UI without getting the way. Well, I ran into a situation today where I had to pull out my old Pixel Perfect design skills, fire up xScope and get down to the pixel level. The shift towards such a wide variety of device screens and accessibility modes made it incredibly cumbersome to be designing things to that level because you’d be tweaking layouts for many dozen screens individually. ![]() In the early days of iPhone development people would often talk about “Pixel Perfect” design, where we would sweat the details right down to the pixel. ![]()
0 Comments
Leave a Reply. |