Chord Progressions Pro
OS :
Version :1.1
Size :492.46Mb
Updated :Aug 9,2020
Developer :Appgorithm, LLC
Ask AI
You can ask the AI some questions about the game
Q{{(index+1)}}{{item}}Ask AI
Pros and Cons from users' feedback
Based on the user reviews, here are three pros and three cons of the app: Pros: 1. **Innovative idea**: Users praise the app's unique concept of visualizing chord progressions, making it easy to create and play. 2. **User-friendly interface**: Reviewers appreciate the app's simple and intuitive design, making it easy to navigate and use. 3. **Helpful for musicians**: Users find the app invaluable for learning and practicing music theory, songwriting, and improvisation. Cons: 1. **Lack of features**: Some users feel that the app is oversimplified and lacks essential features, such as chord voicings and rhythm control. 2. **Limited export options**: Reviewers note that the app's export options are limited, making it hard to share or use the generated chord progressions elsewhere. 3. **Occasional bugs and crashes**: Some users experience occasional bugs and crashes, which can be frustrating and disrupt their workflow. Please note that these are summarized conclusions based on a subset of reviews and may not reflect the opinions of all users.
Game Downloads
IOS
Game Survey
  • Have you played similar games?
      Submission Failed, try again
  • Which part of this game are you most dissatisfied with?
      Submission Failed, try again
  • Is this game too large?
      Submission Failed, try again
  • Can this game cure you?
      Submission Failed, try again
Description
Find yourself using the same chord progressions over and over? Are you unsure what chords sound good together? Do you feel like you've mastered C and G Major, but are at a loss with what chords to use in B flat minor, let alone F sharp Mixolydian? That's exactly the problem that I was having, and this is an attempt to fix that. The following scales/modes are covered (Major, Minor, Harmonic Minor, Dorian, Phrygian,Lydian, Mixolydian,Locrian) for all keys. The more standard key signatures are used (C sharp instead of D flat, B flat instead of A sharp, etc.) First select a scale. Then select the number of chords that you want in your progression. Finally, select the type of ending that you want (end on the Tonic, a Dominant to Tonic, Subdominant to Tonic, just the Dominant, or any chord.) Select the generate progression button and the progression is presented on the screen. Chords are randomly generated to create a progression. But not any random chords, randomly only from the chords that should sound good next in the progression. If you're unhappy with the progression, just select Generate again to create a new one!!! Tap the Play button to hear what the progression sounds like. The Roman Numeral is shown underneath each chord, to show you how it relates to the key. The Tonic chord is shown in yellow to draw your attention to it. The Dominant chord is in green, and the sub-Dominant in Blue. There are also options for Guitar or Piano charts. The goal isn't to have this spit out an entire song (although you could try and do that,) but to use it as inspiration to try chords that you wouldn't normally choose. For a pop or rock type of song you might want to select a 4 chord progression ending with IV-I for your verses and a different 4 chord progression ending with V-I for your chorus. You may find blindly following a 32 chord pattern makes for a fun exercise and find just vamping on that leads to something creative. Maybe a few of the chords in the middle of the progression are ideal, which sparks a new idea. There's no right or wrong, this is meant to spark creativity, and it's up to you (the artist) to decide what works for you. Once you feel comfortable with some of the more common scales, you can then venture into some of the more challenging scales. Roadmap for future releases - -More chord variants -More commonly used progressions
{{descriptionMoreText}}
Comments (0)
{{commentText.length}}/{{maxCommentText}}
{{commentError}}{{commentUserError}}
Failed to load data, try again
  • {{comment.commentUser.substring(0, 1)}}
    By {{comment.commentUser}}{{comment.commentDateString}}
    {{comment.comment}}