edance / gram-gram Goto Github PK

Every time a Postcard is updated, check if it's in a valid state to send with Lob. Trigger the job to send it when it is.

Update UI to have better CTA
Add goals for users who make it to sign up

Clicking logout from the header takes me to the heroku error page

When manually navigating to gramgram.app, it then auto-logs me back in and directs me to /photos. Pretty sure I wasn't actually logged out.

If there's time, I think it's worth investigating this. Let's review some other apps that load IG photos for inspiration.

https://developers.google.com/identity/one-tap/web

Stripe returns a pretty verbose response from Stripe::Charge.create (docs). Right now, we just always set flash[:notice] to a sucess message in Builder#update_payment regardless of the response from create_charge. We should parse the response and set an error message if the payment fails, even if we only support 2 states (success & failure) for V1.

We started the process, but I haven't received any confirmation that we're good to go. We need to make sure this is squared away before launching.

I imagine this was working at some point, but I've had to manually set figure out these values and set them myself in the console to get it working on localhost.

• Build a new model called "order"
• order has many postcards and recipients
• order has one photo for now

This is required for:

• instagram auth (currently just Bill Murray's face)

Found this form to help: https://tableau-mkt.github.io/jquery.addressfield/

Do I need to change the price from dollars to euros? Any other internationalization required?

I've been thinking about adding Google Photos or facebook photos.

Things to write about:

• baby announcements
• graduation announcements
• engagement

Build amp pages with bootstrap for speed:
https://stackoverflow.com/questions/38063272/using-accelerated-mobile-pages-with-bootstrap

Use contentful to power content.

ex. how many workers? https://edgeguides.rubyonrails.org/action_cable_overview.html

Not sure if darker is the word, maybe less transparent. This is just my opinion, but I don't think the CTA button colors are prominent enough. Any changes should apply to the CTA at the bottom of the page too.

We need to add user and postcard metadata to stripe charges so we can more easily debug from the stripe dashboard. This will be easy to do in payments#charge once the checkout flow is hooked up and postcard and current_user are accessible from this action.

• Add meta description
• Add gif for how it works
• Add og image and other open graph tags
• Add share buttons to homepage
• Add share buttons to success screen

Ex.

I think I did this already, but worth one more pass on prod to see if this is handled properly. Main concern is that we'd ship postcards for invalid credit cards and someone exploits this with no guardrails in place.

I really like the photo and font, but I think if you were to send this to your grandma out of the blue you would say something different. Maybe something like Had a beautiful hike at Sonoma State Park last weekend! I'll call you next week! -Evan

It's your picture so feel free to disagree or propose something different @edance

Let's just use 1 generic email address - something like [email protected]

If we don't do this, lots of postcards will end up looking like crap.

Need a Launch Day Plan in place that includes things like:

1. Where are we posting? When? How?
2. Copy for where we'll be posting.

• Create new column
• Associate after charge request in payments_controller

On the payments screen, a failed payment will return a 400 response. Right now there are no additional details returned, although Stripe's API could provide this if we think it's investing in later.

We should show some error message on the payments form when this happens. Right now I'm just showing an annoying alert() in this case.

See payment.html.erb.

We should have some very minimal confirmation screen following a payment that lets users know that their photo was successfully processed and is on the way. Maybe show:

1. Photo preview
2. Recipient name & address
3. Expected delivery date
4. Prompt to Tweet.

There is still some boilerplate copy that needs to be updated.

We need to mail a sample postcard and make sure it looks legit before launching. This should probably include not just us, but 5-10 friends using it and sending their own test postcards, going through the flow themselves. We can refund them in the stripe dashboard.

We need to optimize for the previews that show up when shared on social media.