Skip to content
This repository has been archived by the owner on Feb 21, 2023. It is now read-only.

Document what are android-components and common patterns we see in our applications #33

Open
mcomella opened this issue Aug 1, 2018 · 1 comment
Labels
👩‍🎓user guide Docs for intro or how-to guide on topics we deal with

Comments

@mcomella
Copy link
Contributor

mcomella commented Aug 1, 2018

e.g. how to use:

  • fonts
  • colors
@mcomella mcomella added the 👩‍🎓user guide Docs for intro or how-to guide on topics we deal with label Aug 1, 2018
@mcomella
Copy link
Contributor Author

mcomella commented Aug 1, 2018

Something I wrote up for colors:

Quick rundown on colors: we have a Photon color palette that we ship with android components.

When using colors, we try to use existing references to our color palette because:

  • This ensures we're using the colors we want to be using rather than typoing them and using slightly off colors
  • It reduces the overall number of colors defined in the app, making things a little smaller and simpler
  • Makes dialogue between UX and engineering easier: "what color is that?" "Oh, photonGrey10." "Ah, that should be photonGrey20!"

There isn't a great way at the moment to go from hex code to color name besides grepping through the file in the android-components repository. Usually, Amin will mention the color name and it won't come directly as hex just from the mocks.

Caveat: the android-components project doesn't define colors with different alpha values, however: in this case, we define redundant colors in the project like, photonGrey10_a80p (photon grey 10 with 80% transparency) and try to re-use those.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
👩‍🎓user guide Docs for intro or how-to guide on topics we deal with
Projects
None yet
Development

No branches or pull requests

1 participant