Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1/30 Updates #2

Open
7 of 8 tasks
bbertucc opened this issue Jan 30, 2023 · 8 comments
Open
7 of 8 tasks

1/30 Updates #2

bbertucc opened this issue Jan 30, 2023 · 8 comments

Comments

@bbertucc
Copy link
Member

bbertucc commented Jan 30, 2023

A few updates from the client:

  • Include commas in number (ex. 100,000 to 1,000,000)
  • Update formula to "per second" increments.. 0.04 tires/sec, 23.15 bags/sec, .01 trees/sec
  • Include a dot with 2 digits following each number (ex. 1,000,000.04) to show movement by second (more constant versus waiting a minute for action).
  • Once the clock is started, it needs to be able to run in the background (keep incrementing)
  • Change subtitle to ‘Cumulative Eco-Offset of Malarkey Shingles’
  • Add images of tires to the slideshow.

New Items

  • Need to make sure everything fits into a screen on a horizontal 11" iPad.
  • Make design changes, as displayed here

The client would like to have these complete within the next two weeks.

@azdak lmk if this requires any additional time on the budget. if it doesn't, and you have no further questions, we can change the label to "approved" and move forward.

@bbertucc bbertucc added this to the 1/30 Updates milestone Jan 30, 2023
@azdak
Copy link
Contributor

azdak commented Jan 30, 2023

These 4 are fine:

  • Change subtitle to ‘Cumulative Eco-Offset of Malarkey Shingles’
  • Decrese white space above and below icon/counting area
  • Add images of tires to slideshow.
  • Include commas in number (ex. 100,000 to 1,000,000)

but for:

  • Update formula to "per second" increments.. 0.04 tires/sec, 23.15 bags/sec, .01 trees/sec
  • Include a dot with 2 digits following each number (ex. 1,000,000.04) to show movement by second (more constant versus waiting a minute for action).
  • Once the clock is started, it needs to be able to run in the background (keep incrementing), or quickly update itself with the lost time every time someone comes to the site for the most up-to-date numbers.

I'd say are out of spec, and 1) would probably mean changing how we're doing the animation- it already updates once per second, but with hundredths, it's going to be going really fast lol (too fast for the odometer-style, I think). 2) For the last issue- really need to understand better the use case, bc as described it'd need some type of serverside storage (and an admin login) to be able to set the initial starting time globally for all users (which was not what was originally asked for).

@bbertucc
Copy link
Member Author

bbertucc commented Feb 9, 2023

@azdak -

They want to see the new numbers in the odometer style with deciminal points before they decide what to do.

They also need to have the numbers saved in the background somehow. It will be running on multiple iPads that should be synced. (To get the updated number, On page load.. I wonder if we can do a formula that updates each session that quantifies the amount of time since Feb 3, when the counters should have started ticking?)

@azdak
Copy link
Contributor

azdak commented Feb 9, 2023

They also need to have the numbers saved in the background somehow.

I mean- it could just perpetually run from a hardcoded global start datetime and then they'd all match, but if that datetime *isn't" hardcoded and needs to be set by a user for all possible instances, there has to be some type of state management/backend storage. Either is possible, but the latter is going to take longer.

@bbertucc
Copy link
Member Author

bbertucc commented Feb 9, 2023

I mean- it could just perpetually run from a hardcoded global start

For this version, they are okay with having a hardcoded start time.

@bbertucc
Copy link
Member Author

A note from the client around the design changes:

Below is a link to the updates. The .AI file is in the folder - since you have the majority laid out, if you can get your layout as close as possible to the .AI file, that would be great. And I realize some things may change to meet your requirements to work well.

Also, in the folder is an Images folder. These are the images we'd like to do a slow rotation in the image box. The PDF for reference shows what they are, and in the order we'd like them.

If you have questions, reach out!

@azdak
Copy link
Contributor

azdak commented Feb 13, 2023

Estimate is 4 hours (2 for hardcoded start date & hundreds-place increment, 2 for everything else)

@bbertucc
Copy link
Member Author

Attaching the updated mockups @azdak

The changes:

  • New section beneath the fold
  • Removed green line under title
  • Updated headline content.

Does this change your estimate?

Screenshot 2023-02-14 at 1 58 51 PM

@azdak
Copy link
Contributor

azdak commented Apr 18, 2023

Changes up here. For the tire images... we need the tire images haha. For the ipad thing- haven't tested, don't have one, but should be about the right size to fit everything, in portrait.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants