glifchits/bluum

mobile app that lets you track coffee beans you've tried (React Native with Apollo GraphQL backend)

Hello!

👋 I am a software generalist primarily building with React and Python.

📫 You can find how to reach me at https://georgelifchits.ca/

bluum's Issues

Backend for uploading images

Hookup adding new coffee to DB

• Backend GraphQL mutation
• Apollo (client) hooked up to frontend mutation

Set up bare domain support for getcoolbeans.com

Currently we have a redirect to www. However going explicitly to https://getcoolbeans.com will fail since the bare domain is not supported.

Need to do this via cloudflare it seems.

Hook up adding new roaster to DB

• Backend GraphQL mutation
• Apollo (client) hooked up to frontend mutation

Fix homepage <> search navigation on iOS

Mock up Community Rating and User Rating Component

User Creation

Need some way to create user profiles. Would be cool if ppl could log-in using Facebook or Google.

Acceptance Criteria

• User model in the DB
• API for creating/authenticating users via the React Native client
• User signup/login UI in the app

Create a nice looking null state when there are no brews for a coffee

Landing Page

Add coffee data to the DB

Landing page background image cover

Should not see that whitespace at the bottom with this screen size

Hook up Search Results to Coffee Profiles

Acceptance Criteria

• Tapping a search results should bring you to that coffee's profile

UI for Adding Brews

Requirements

• Rating slider
• Brew method dropdown
• Notes text input
• Grind Coarseness slider
• Amount of coffee text input with unit dropdown
• Amount of water text input with unit dropdown

Photos and tasting notes can probably be skipped in V1

Mockup

Wishlist/favourite

• Model
• API
• frontend

Mock up different coffee states (Have Tried, Want to Try, Haven't Tried)

Make Coffee Info the main tab and have the bottom button CTA be contextual based on the active tab.

Add Coffee Screen UI

Fix screen routing (specifically hitting back on Coffee Profile)

Create coffee profile API

Acceptance Criteria

• API to retrieve details for specific coffee

Write tests

Move fast but don't break things

Wise to do for continuous deployment: #45

Deep dive on refreshing after mutations

Whenever new brews/coffees/roasters are added, so far I've been doing granular manipulations to the Apollo cache using the Mutation update={(cache, { data })} prop. There must be a better way, because the Query and Mutation components are so nice and declarative and the cache updater callback is not.

Consider JWT best practices or alternative stateless authentication mechanism

Token refreshing: https://security.stackexchange.com/questions/119371/is-refreshing-an-expired-jwt-token-a-good-strategy

Best practices: https://dev.to/neilmadden/7-best-practices-for-json-web-tokens

Alternatives: https://neilmadden.wordpress.com/2017/03/15/should-you-use-jwt-jose/

Select/Create Screen for Roasters

Requirements

• User can input a search term
• Return roasters that match the search term
• Append an extra card to the list that allows the user to add a new roaster

Also, we should try and make this container re-usable for other objects like tasting notes, regions, or brew styles.

Consider removing Express and using straight up Lambda handler for backend

Express can do a lot of things, but we probably don't need most of them – the server is essentially the one graphql endpoint, seems overkill to have Lambda wrap an entire server.

Prettier loading states

Subjective coffee ratings

Support the concept of an overall coffee rating. A user should be able to assign a rating to any coffee that is not tied to any brew. A nice way to think of this is a user's subjective, "holistic" opinion of coffee beans.

• Implement DB/API for this stuff, associate with users
• Frontend to assign ratings

UI for My Coffee list

Requirements

• User can sort coffees by Date Added, Roaster, and Roast Type
• User can search coffees
• Render list of coffees that the user has brewed

We can probably leave out filters for V1

Mockup

Wireframes

Acceptance Criteria

• We feel pretty good about implementing the wireframes as a V1

Add a new roaster screen

The screen which provides a form to add a new roaster to the DB. Follows up on #24 – its what happens when the user decides to add a roaster that didn't show up in the search.

Build UI for Coffee Profile

Requirements

• Displays Basic Info about coffee at the top (name, roaster, roast type, rating)
• User can toggle between two tabs: My Brews and Coffee Info
• In the My Brews tab, brew history is displayed and sorted by most recent
• In the Coffee Info tab, show description and any other info we have on the coffee

Mockups

Update dependencies

Make sure things don't get out of date

Social logins for user authentication

Acceptance Criteria

• Choose social media accounts to support
• Implement user creation/auth for social logins

Implement continuous deployment

It would be great if a push to master could update the server and even publish a new version of the client.

Associate brews with users

• Ensure that new brews are created for the authenticated user
• Ensure that past brews are only fetched for the authenticated user
• Model
• API
• Frontend

DB query performance monitoring

Add something like pgBadger so we can see which queries are being executed the most and find ways to optimize them

Handle Text Overflows

Make the iOS status bar transparent/colour matching

Sorting lists on the backend

Implement search filtering

Deploy backend

Acceptance Criteria

• API has an https endpoint

Hook up domain to webflow site

• @seanjyoung give webflow credentials to @glifchits
• @glifchits configure domain to point to webflow
• https://getcoolbeans.com/ works

Fix app crash

To reproduce:

1. Add a new coffee
2. Go to the coffee details page for the new one
3. Go to "More info"

Expected: shows more info

Actual: crashes, goes to home screen, Apollo cache empty

UI for Looking at a Past Brew

Requirements

• Shows the properties of the brew that the user had made
• Nothing can be changed, this is read only

Mockup

Make a logo

Backend for adding new brews to DB

Style the App

Screens to Style:

• Home Screen
• Search Results
• Add New Coffee Form
• My Coffee
• Coffee Profile
• Add Brew

Publish App

Grind coarseness bug

Create coffee list/search API

Acceptance criteria

• API allows a client to filter coffees in the DB based on name/roaster

Look into missing brew metadata

UI for adding new coffee

Acceptance Criteria

• A screen where user can enter all relevant info for creating a new coffee