rbannal86

Keybase proof

I hereby claim:

• I am rbannal86 on github.
• I am rbannal (https://keybase.io/rbannal) on keybase.
• I have a public key ASAnBCqoC54QMyt387zdDEpqMp_pEDBH_gMMRUNROBVSDwo

To claim this, I am signing this object:

rbannal86

briefPal Feedback:
  I sent the briefPal link to a few people who I knew would view the app on mobile. I main feedback dealt with the styling on mobile devices, which I attempted to correct. Th rest of the feedback dealt with potential applications of the project, which aren't immediately actionable or relevant to the assignment, but still an interesting look at how users see potential interactions with the app.

rbannal86

Project Name: briefPal

Wireframes:
  Welcome Screen: https://repl.it/@AlexBannow/briefpalwelcomescreen
  Create Letter: https://repl.it/@AlexBannow/briefpalcreateletter
  First Letter Sent: https://repl.it/@AlexBannow/briefpalfirstlettersent
  Respond: https://repl.it/@AlexBannow/respondbriefpal
  User Profile: https://repl.it/@AlexBannow/userprofilebriefpal

User Flows:

rbannal86

As a new user, I should be able to:
  Find out what the app does
  Create an account
  Start writing the first letter
  View rules
  
As a returning user, I should be able to:
  Be alerted of new letters
  Respond to a letter
  Create a new letter

rbannal86

Even though there are a few existing pen-pal apps, I intend for briefpal to be as simple as possible. Instead of collecting badges or turning letter-writing to strangers into a game, this app will allow for people to briefly connect through the writing of three letters- the initial letter from the first user will establish the topic, get sent out to a random user, and then responded to by that random user. After the response is sent, the initial user can respond one more time. After that, the exchange is over. The goal is to create a moment. There will be no friend list or choice to continue talking to the matched user. The intent is not to create a social network.

This app can meet many different needs: simple human contact, writing practice, or flexing creativity. Even though there will be no sustained contact between the letter-writers, the hope is that each person will walk away having their needs met. The user will be able to save their correspondence, but there will be no indication of who wrote the le

rbannal86

drop table if exists bookmarks;

create table bookmarks (
  id INTEGER primary key generated by default as identity,
  name text NOT NULL,
  url text NOT NULL,
  description text,
  rating INTEGER NOT NULL,
  CHECK(rating > 0 AND rating < 6)
);

rbannal86

Headline:
Cooking up code, one line at a time.

About Me:
As a kid, I spent most of my free time in front of a computer playing games. In high school, I became interested in what was going on behind the screen. I found the concepts of coding engaging and the work challenging, but I didn't think of it as a future career. I enrolled at Western Michigan University as a history major, switched before the first day of classes to microbiology, and eventually transferred to the University of Michigan where I graduated with a BA in English Literature and Language. After college, I pursued personal creative projects, like poetry and webcomics. To make ends meet, I got a job in food-service. To my surprise, I fell in love with the creativity, the need for fast-paced problem solving, and the feeling of being part of a team. After ten years and a journey that ended with me being a pastry chef, I realized that a kitchen wasn't the right work environment for me. 

Creativity, problem-solving, and teamwork were always the h

rbannal86

https://docs.google.com/drawings/d/1rUBMA49er8xoP_5uSsdm2x5k8Z8WXsX09XYAwdq12d0/edit?usp=sharing

The above is the mock up for the full-screen and potentially tablet version of the portfolio site.

https://docs.google.com/drawings/d/1BnzEytgZXa7gjjo7zUojRl6Dzy5hkACr0-XLFhB7mZ8/edit?usp=sharing

The above is a mock up for a mobile design.

rbannal86

1. endpoint: https://www.googleapis.com/youtube/v3/subscriptions
   filters is required: can accept a string that returns a channel id (channelId)
   maxResults is optional: can accept an unsigned integer from 0 to 50, with a default of 5
   order is optional: cann accept a string (alphabetical, relevance, unread)
   
2. Statue of Liberty: https://maps.googleapis.com/maps/api/geocode/json?address=Statue+of+Liberty=YOUR_API_KEY
   My Address: //maps.googleapis.com/maps/api/geocode/json?address=2311+Buckingham+Road,+Ann+Arbor,+MI&key=YOUR_API_KEY
   Requires paid subscription, added "=YOUR_API_KEY" to each URL.
   
3. Meetup API

rbannal86

Client-Server Analogy:

You are a client. You walk into a tiny candy store and, immediately, you realize that this is a strange store. There's a small space,
a counter, and a person behind the counter. There is a dark doorway behind the person. You ask the person for a piece of candy corn.
That person walks into the dark doorway and returns with a piece of candy corn. That dark doorway leads to the server. You, the client,
requested a piece of information (candy corn) and the strange person (API) retrieved it from the room behind the dark doorway (server).


Request/Response Cycle Diagram: