docsmage / relaxio Goto Github PK

• Use HTML/CSS to display/style page title, app icon, and list of sound placeholders
• Create SoundController.js file which will control the display and interactions of sounds
• Separate controller into it's own folder

Disable ability to adjust volume OR hide the volume bar for sounds which are not currently playing

Any website or application that has a login system should be using an ecrypted connection.

There's only so much valuable data that an attacker could get by intercepting a Relaxio login (so far?), but TLS will give a little extra protection for users who unfortunately reuse passwords across multiple services, and could help prevent cleartext email addresses from being added to a spam list.

• Add front-end project starter kit files
• Update index.html w/title info
• Add module, state, ui-router, & controller to app.js
• Have page display title info in controller

• Ensure that multiple songs can play at once
• Ensure the pausing one sound does not affect other sounds
• Optional: write Jasmine tests for behavior

• Download sound files, save to assets/sounds
• Instantiate them using Buzz API (can't use YouTube, as it turns out)

• Create SignUpDirective and SignUpController
• Implement functionality for users to initially sign up
• Implement Sign-up template as pop-up
• Connect sign-up and login pop-ups via "Already have an account?" and "Don't have an account yet?" messaging

• Evaluate and optimize app as needed for mobile responsive behavior
• Add in designs from Gisele
• Test on multiple devices
• Optional: write tests in Jasmine enabling this functionality

• Create templates for About and Contact pages
• Create MenuService and MenuController
• Add functionality to allow users to be directed to 'about' and 'contact' pages
• Optional: have them be external links so users can link their friends directly to those pages as desired

• Create SoundService with this functionality
• Update SoundController w/functionality
• Separate service into a service folder

• Update SongService and SongController to ensure that the song will loop when it comes to it's end
• Optional: write tests in Jasmine to ensure this behavior

• On SavedMixes template, add functionality for user to indicate a 'default mix'
• Add functionality into SavedMixesService, SavedMixesController && MainController that a 'default mix' can be established and should play when the user first lands on a page

• Design graphic in CSS and implement in index.html
• When clicked, should open into a menu item which lists About and Contact

• Create VolumeControl & VolumeService for users to update individual volumes
• Implement functionality for master volume as well

• Use Facebook API to implement signup and login functionality
• Visually depict 'Sign up / Log in via Facebook' icons as needed
• Store user data in Firebase
• Ensure that if that email address already exists in our database, user will receive message stating that they have already an account created via email

Bug: If other sounds have been previously play/pause toggled, they will unpause along with the ones that were previously paused the moment that master play/pause is used.

Preferably light purple gradient

There's a tech security adage I heard somewhere that says the best way to protect some data is to not have it. That is, someone breaking into your system can't steal any data that doesn't exist. Users would not have to trust your application, and you would not have to worry as much about protecting your login backend, if you implemented alternative ways of saving user mixes.

Such as local storage. Local storage, I'm guessing, would be simpler to implement, and greatly reduces the "attack surface" for an application like Relaxio. One downside of local storage is that there's not really a good way for users to take the data with them to other devices or browsers.

Another possible solution would be to create a URL for the current mix, where the sound sources and volume levels are encoded as URL fragments or query strings. This might be a little more complex than local storage, but it would allow users to save their mixes as bookmarks, which all the major browsers can sync across devices, or which users can export and import to different browsers.

Just a thought. You already have a login system in place, so you don't necessarily have to throw that away; local storage or a custom mix URL could also work as just another option for users. But it occurred to me that maintaining a database of user data, any kind of user data, is a responsibility I would personally prefer to avoid if possible, so I'm just saying.

• Add in YouTube API and use to instantiate sounds
• Store sound names and URLs in Firebase under 'sounds'

• Create LoginController and LoginDirective
• Implement functionality in those files to allow users to login via email
• Store login info in Firebase
• Utilize cookies to ensure that by default users are signed in
• Add login button via HTML/CSS
• Add pop-up template for logging in

• Create SavedMixesService and SavedMixesController
• Add a 'Save' button via HTML/CSS
• Allow user to give a title to their saved mix, let them know visually which sounds are included
• Create a popup SavedMixes template to display this functionality
• Implement functionality to recognize user login and store saved mix title and URLs via Firebase
• Optional: let them know if that sound is already saved under their info

This page should list the username, password, list of saved mixes, and the sounds included in each mix.

As of right now, clicking anywhere outside of signuppopup makes it disappear - however, taking action such as clicking 'signup' or 'login' currently does not send the modal away. This should not be the case.

Initial investigation into this issue lead me to http://stackoverflow.com/questions/23762323/is-there-a-way-to-automatically-close-angular-ui-bootstrap-modal-when-route-chan I attempted to implement the top solution by updating the .run statement in my app.js file. This did not work.

Next, I tried adding ng-click="closeModal()" to each URL in signuppopup.html, as in Sign up to save your mix! This also did not work, despite the fact that NavCtrl is the controller for that file, and that the closeModal function in NavCtrl appears to be written correctly according to the documentation provided by angular.

At this point I am stepping back from this issue to try fixing it again later. Submitting here to document my progress and also to separate it out as a different issue from issue #43.

• Pull Twitter API into SocialMediaService and SocialMediaController to enable 'tweet' button
• Depict visual 'Tweet' button on index.html

• Similar to Pandora, create a page for a soft landing page which segues the user into the main page
• Allow white noise to play while user is on the landing page

Currently, to change the volume for a given sound source, you have to click and hold on the the little nub (the div.thub element) and drag left or right. When I recently started using Relaxio again, I instinctively expected to be able to click on the volume bar where I want the volume level to be.

• Pull in Facebook API info and add to SocialMediaService / SocialMediaController
• Visually depict 'Share' button on index.html

Grey out sounds and make them unclickable when master is on pause.

• Use Twitter API to implement signup and login functionality
• Visually depict 'Sign up / Log in via Twitter' icons as needed
• Store user data in Firebase
• Ensure that if that email address already exists in our database, user will receive message stating that they have already an account created via email or Facebook

Based on feedback received after initial launch

• Use HTML/CSS to allow active songs to have a 'soft glow' around them
• Ensure hovering over sounds appropriately brings up the play/pause button

• Add volume controls via CSS, allow users to update via HTML