Be nice. Or else.
A Designer Joined over 5 years ago via an invitation from Allan G.
the calculate button is disabled even when all fields are filled in.
I think your overall pricing structure and flow need some work. I'd rethink this approach completely with whoever is in charge of PM.
The flow doesn't make any sense, based on your pricing structure (IMHO). For instance, I can add 20 beacons to my cart but select the BASIC nine beacon plan.
Instead, I would lead with the hardware, and suggest the right software package, based on the beacons added to the cart (though I even question the package model you have here). So you would have a two-part flow.
Also, the font is too small in the plans area. Suggest at least 14-15 pt.
Also, fix positioning the checkout button to the bottom of the screen is unconventional, and likely to be missed (I missed it).
tl;dr no discoverability
The point of grid is to also apply semantic naming to your grid areas. This increases code readability and understanding. Here is a good read for the uninitiated:
I have mixed feelings about this kind of work. On one hand, it's a cool transition, but actually building something like this would be incredibly difficult from a UI engineering perspective, so I wouldn't do it for a "real" product. I suppose though that these kind of things are OK for showing off in dribbbbble.
Both. Principle is for micro interaction. Flinto is for flows (but can do some Micro interaction stuff). Neither of these products is difficult to learn.
Learn Flinto or Principle and Framer for work, After Effects for fun.
OK, first... this is completely awesome!.
Second... How does this fit into my gulp webpack SCSS babel jekyll asset pipeline?
Our IT corporate overlords think this is a porn site for some reason.
Be nice. Or else.
Designer News is a large, global community of people working or interested in design and technology.