A mobile app for music written in flutter

music

download and play songs from your phone.
optionally you can sync with firebase, allowing easy use of multiple devices.

easily play and download songs

view all songs and by artists

automatically generated albums as well as custom ones

shuffle and view queue

this app is the mobile version of this app, which is out of date and is soon to be updated.

if you have any issues or suggestions, feel free to open a pull request or file an issue

if you wish to customize or learn more about the project, go here.

download and installation

for android, you can directly download a built version of the latest release here. first generate the api keys and then download the apk from the latest release.

if you are on ios or want to download and build the project yourself, follow the steps given below.

api keys

the app requires a napster api key, to function. you can also optionally add firebase for syncing.

steps to create the api keys can be viewed here.

once you have those created, you can move onto running the app.
you will need to enter the api keys directly in the app.

build dependecies

first install flutter. after that run:

flutter pub get

this will install dependecies.

testing

to run the tests, written for the app, run:

flutter test

running without a regular installation

if you wish to test the app to see if it works, connect a device or run an emulator. to start the profile mode app (runs faster than debug mode, but doesn’t have the developer functionalities), run:

flutter run --profile --flavor dev

building

for android:

signing the app:

• create a keystore

  if you have an existing keystore, skip to the next step. if not, create one by running the following at the command line:

  on mac/linux, use the following command:

  keytool -genkey -v -keystore ~/key.jks -keyalg rsa -keysize 2048 -validity 10000 -alias key
  

  on windows, use the following command:

  keytool -genkey -v -keystore c:usersuser_namekey.jks -storetype jks -keyalg rsa -keysize 2048 -validity 10000 -alias key
  

  this command stores the key.jks file in your home directory. if you want to store it elsewhere, change the argument you pass to the -keystore parameter.

  • the keytool command might not be in your path—it’s part of java, which is installed as part of android studio. for the concrete path, run flutter doctor -v and locate the path printed after ‘java binary at:’. then use that fully qualified path replacing java (at the end) with keytool. if your path includes space-separated names, such as program files, use platform-appropriate notation for the names. for example, on mac/linux use program files, and on windows use “program files”.
  • the -storetype jks tag is only required for java 9 or newer. as of the java 9 release, the keystore type defaults to pks12.

• reference the keystore from the app

  create a file named android/key.properties that contains a reference to your keystore:

  storepassword=<password from previous step>
  keypassword=<password from previous step>
  keyalias=key
  storefile=<location of the key store file, such as /home/<user name>/key.jks>
  

building apk:

• ‘fat’ apk

  flutter build apk --flavor prod
  

  this will build a ‘fat’ apk, which contains code compiled for all architectures, which means it can run on all android devices.

• split apks

  flutter build apk --split-per-abi --flavor prod
  

  this will split it into different apks, based on the architecture which results in smaller app sizes, but it only works on phones with the specific architecture.

once finished building, the apk will be available at build/app/outputs/flutter-apk/app-prod-release.apk. to install, either transfer the apk to your phone and install, or connect your device via usb tethering and run:

flutter install

you may be shown this popup when installing the app:

you can safely click ‘install anyway’.

for ios

see flutter’s ios release documentaion.

issues

ios

the app was built with an android testing device and so it may not function fully as intended in ios. in general the ui will look and work the same, but platform specific things like notifications may not. for example, android allows for progress notifications while ios does not.

firestore

there is a ios/runner/googleservice-info.plist file, this contains a mock plist file, for connecting with firebase since the cloud_firestore plugin for ios requires that exists, or else wont build. this is not a very good solution.