Skip to content
This repository was archived by the owner on Mar 14, 2022. It is now read-only.

Latest commit

 

History

History
27 lines (16 loc) · 1.7 KB

File metadata and controls

27 lines (16 loc) · 1.7 KB

REPORT

Overall

My background is 90% technical and 10% business needs, with poor skills in design (color theory, hierachy and other concepts I am familiar with and never implemented it).

I've made several mistakes regarding to the organization of styles:

  • No clear organization of responsability (where should I put the css?, inline styles?, it's all bundled together).
  • No sub division of components
  • No testing implemented

To be really honest, I could keep going on the organization but I was very anxious and worried of not being able to make it to the interview (might be a lot of competition out there).

Architectural decisions

  • This mockup is based on Preact for the sake of simplicity in bundle size and to try out new things (i've never done a formal app with this library).
  • With the same philosophy of low bundle size, also installed date-fns specially for those date calculations (is this date in-between the range given?)
  • I've implemented an in-memory DB lowdb as a mockup to easily extend it into a real app.

Regarding Mission 1

I couldn't replicate the visual capability of a search bar using two date ranges. I've tried using libraries but they were exceeding the gzip size of the entire bundle (> 500kb), so I took a decision to leave it out behind and keep it perfonmant.

Regarding Mission 2

Related to the assignment the extended design should allow user to inspect multiple email bodies at once I assumed that is referred to the mail chain, but I had no clue in design and I wasn't feeling comfortable doing it without a design guidance.