/foundations-1-projects

https://trianacerda.github.io/foundations-1-projects/

Primary LanguageCSS

References

SimplePlay

SimplePlay is a frontend app that was specifically designed for a user who is visually impaired that also experiences mobility issues. SimplePLay provides an ability based UI feature to give control of a preloaded playlist created by an outside user. SimplePlay is tailored to be inclusive in regards to specific barriers, allowing an individual to access wonderful music. Along with beautifully designed features, SimplePLay has a grab bag of wonderful colors to chose from.

SimplePlay resolves a specific problem related to visual and mobility barriers. SimplePlay was designed with a team member's immediate family in mind. Most people love music and the inability to independently access this can be difficult. SimplePlay allows any user to access pre-loaded music with 2 touches. The first touch is to open the app, second is to start playing music. The playlist is previously selected by an exteral user. SimplePlay brings accessibility and great tunes for all. Specifically, SimplePlay brings hope back to someone who loves music but lost the ability to easily access it.

Tools: GitHub, JavaScript, CSS

Dev Team: Alice, Evon, Justin, and Triana

Credit section

Justin

  • first page functions
  • settings/about us page
  • TDD Uploading Music App.png…

Triana

  • first page functions
  • data collecting
  • TDD

Alice

  • first page functions
  • buttons
  • shuffle function

Evon

  • first page functions
  • function guidance
  • shuffle function

foundations-1-projects

Mission Statement: "Keep it simple and smart for Triana's dad"

Group Agreements

MANDATED BREAKS

  • Openly commicate about scheduling issues and/or anything.
  • Personal conflicts: side bar with a DM, address it when it comes up - - please dont let it linger.
  • Group conflicts: limit disagreements to 30 minutes-- neutral teammates set the clock if noticed.
  • Only solo/pair struggle for up to 15 minutes before asking for help.
  • Be open to listening to your teammates.
  • DONT merge unless every group members has had eyes on it.-- DONT BE A BOB!

Work styles: solo, paired, and mob programming

  • mob/pair programming: working on something that isn't your immediate strength

who talking about what?

  • everyone okay with talking-- everyone communicated this with silence.

Schedules--

9-915 SCRUM

  • What is the objective for today?
  • Visuals for app pages

1150-12 SCRUM

  • quick check in
  • set up for after lunch tasks

12-1 LUNCH

545-6 REFLECTION

  • Who is working on what EXACTLY after hours?
  • One thing that went well today?
  • One thing we would like to improve on?
  • One thing to continue for tomorrow?
  • One thing we learned today?

What is needed to be a deployable app - meeting expecatations of lab/user

  • front page that works and specifically for visually impaired people
  • large button: play/pause (skip/back)
  • box for text(title)
  • link for second page: working on placement - possibly upper right
  • different clicks for users and/or different buttons

STRETCH

  • color scheme options: different versions of color blind
  • screen reader
  • second page for form of input fields for desired song/audio links (work in progress)
  • settings for admin to adjust user page

NOTES

Screen Shot 2021-07-26 at 10 51 17 AM

Presentation Day

  • Your planning process -- show us your Miro board
  • Your data model -- how and why did you choose to model your data the way you did -music-data:structured to what we know as local data, localStorage, assests data:btn(pictures-original), css files: rendering css data
  • Your local storage -- what is being saved when and how is it updated -playlist, color schemes, shuffle is on
  • The hardest technical problem you faced and how you solved it -coloring changing schemes, imaging what it could do and what we knew we could do. -working within our toolbox: music-data, everyone handled it, very organized and planful, group agreements.

Music App (2)

Scheme API