Eventuell können wir für Browser, die ES6 vollständig unterstützen, uns das babeln sparen und für diese Browser einen gesonderten Build ausliefern.

Currently one is signed into the Spotify account the moment a party is joined. This is unintuitive.

Generalization of #24

_redirects im Repo erstellen

Spotify just sent a mail stating that in the future, all requests against their API endpoints have to be authenticated. We'll have to adapt to that.

Momentan ploppt der Vote-Button bei Änderung des Statuses noch ziemlich hart rum, das ist unschön.

Artists, Cover-, und Hintergrundbilder

iron-list ploppt bei Änderungen in der Reihenfolge der Items noch hart rum, das muss für den Release schön smooth werden.

There are layout bugs on iOS when rubber banding.

Fürs Playback

When one votes a new track into the Queue, it does not appear in the local queue, only on the queue of other devices.

Under the Bridge is actually next, but not shown (also notice the broken visuals):

As soon as the track is over and playback skips to the next track, everything turns out fine:

Momentan schiebt das app-drawer-layout die Seite auf volle Breite und zeigt den Drawer seitlich fix an. Man muss schauen, wie man den Voting-Screen auf großen Bildschirmen generell implementiert.

Wenn die Leute einen Direktlink eingeben sollen sie, wie bisher auch, automatisch auf die richtige Party weitergeleitet werden, falls möglich. Die Funktionalität muss im Root-Routing eingebaut werden.

We need a worker process somewhere in the cloud that is responsible for updating the "order" values after votes have changed.

We want to allow the party host to require his guests to sign in via a social login provider to be able to vote. This will prevent vote cheating once and for all (modulo multiple accounts).

So Sachen wie die Polymer-Lizenz sollten nachher im Produkt irgendwo zu finden sein, damit da kein findiger Anwalt was zu meckern hat.

Uglify macht mit dem JS irgendwas, was nicht mehr von V8 geparsed werden kann.

Fehler aus #1

Currently we do not know what happens when e. g. the User pulls out the AUX cable or is disconnected from AirPlay. Those cases need to be figured out.

Erweiterung von #1

Sobald Polymer 2.0 fertig ist, kann / sollte das Projekt darauf migriert werden, damit man auf dem neuesten Stand bleibt.

#8 wäre ebenfalls cool mit Polymer 2.0.

When running the app I am getting authentication errors.

I have setup an firebase and AWS lambda function.

For the app, I use the following .env

FIREBASE_API_KEY="aaaaaa"
FIREBASE_AUTH_DOMAIN="festify-xxxxx.firebaseapp.com"
FIREBASE_DB_URL="https://festify-xxxx.firebaseio.com"
SPOTIFY_CLIENT_ID="yyyyy"
SPOTIFY_TOKEN_SWAP_URL="https://zzzzz.execute-api.eu-central-1.amazonaws.com/dev/exchange"
SPOTIFY_TOKEN_REFRESH_URL="https://zzzzz.execute-api.eu-central-1.amazonaws.com/dev/refresh"

Directly after starting it, the app crashes.

logcat:

03-02 22:40:02.849  1757  3038 W ActivityManager: Ignoring remove of inactive process: ProcessRecord{6006db6 0:rocks.festify.app/u0a61}
03-02 22:40:02.960  1757  3038 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=rocks.festify.app/.MainActivity bnds=[773,1102][997,1326] (has extras)} from uid 10012 on display 0
03-02 22:40:03.043  1757  2407 I ActivityManager: Start proc 3065:rocks.festify.app/u0a61 for activity rocks.festify.app/.MainActivity
03-02 22:40:03.112  3065  3065 W System  : ClassLoader referenced unknown path: /data/app/rocks.festify.app-1/lib/x86_64
03-02 22:40:03.290  3065  3065 F libc    : Fatal signal 6 (SIGABRT), code -6 in tid 3065 (cks.festify.app)
03-02 22:40:03.343  3084  3084 F DEBUG   : pid: 3065, tid: 3065, name: cks.festify.app  >>> rocks.festify.app <<<
03-02 22:40:03.422  1757  1822 I WindowManager: Destroying surface Surface(name=Application Error: rocks.festify.app) called by com.android.server.wm.WindowStateAnimator.destroySurface:2014 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:881 com.android.server.wm.WindowState.destroyOrSaveSurface:2073 com.android.server.wm.WindowSurfacePlacer.performSurfacePlacementInner:429 com.android.server.wm.WindowSurfacePlacer.performSurfacePlacementLoop:232 com.android.server.wm.WindowSurfacePlacer.performSurfacePlacement:180 com.android.server.wm.WindowManagerService$H.handleMessage:8079 android.os.Handler.dispatchMessage:102 
03-02 22:40:03.766  1757  3089 W ActivityManager:   Force finishing activity rocks.festify.app/.MainActivity
03-02 22:40:03.908  1757  2407 I ActivityManager: Process rocks.festify.app (pid 3065) has died
03-02 22:40:04.322  1757  1822 I WindowManager: Destroying surface Surface(name=Starting rocks.festify.app) called by com.android.server.wm.WindowStateAnimator.destroySurface:2014 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:881 com.android.server.wm.WindowState.removeLocked:1449 com.android.server.wm.WindowManagerService.removeWindowInnerLocked:2478 com.android.server.wm.AppWindowToken.destroySurfaces:365 com.android.server.wm.WindowStateAnimator.finishExit:565 com.android.server.wm.AppWindowAnimator.stepAnimationLocked:427 com.android.server.wm.WindowAnimator.updateAppWindowsLocked:196 

Für #15

Currently a firebase cloud database is needed.

Use case:

Support grilling hut "Grillhütte" parties where no internet connection is available.

The question is, if an other, self-hostable Firebase alternative can be used.

If the app is put into the background by the operating system, it loses all of its internal state. When the app is resumed, the user is presented the start screen.

Nötig für #7

When the app is playing in the background and skips to the next track, the queue view does not update accordingly, if one switches back into the app:

Actually, alt-j was playing at that time:

This is probably linked to #38.

Für #15

Es wäre cool, wenn der Fanart-Hintergrund beim Übergang smooth faded und sich dezent bewegt (Ken Burns etc.).

Momentan hat das vulkanisierte Bundle etwa 1,6MB. Das ist für den Release etwas viel und muss durch Minification and Tree-Shaking reduziert werden.

This could be a really tough one to solve.

Momentan gibt es Probleme mit firebase-document, weil bei der virtualisierten iron-list zu oft der Pfad gesetzt wird, alsdass ein stabiles Abrufen der Votes möglich wäre.

Lösung: Es soll ein zweiter Vote-Index erstellt werden, der nach Party->User ID->Votes sortiert ist. Dann kann man einen Firebase-Listener auf das gesamte Vote-Objekt des Users legen, und sich daraus alle Daten ähnlich wie bei den Metadaten ziehen.

Right now it's possible to build Festify with missing env variables which silently leads to bugs / breaks the build.

It's currently empty.

Currently it's not possible to skip a track without debugger access.

I think we turned it off to prevent that weird bug with app-header-layout, but since we got rid of it a short while ago, we should turn it on again.

When there is only one track in the queue and one skips that, the player progress bar doesn't stop.

The party view currently has background colors, which are based on grey, rather than the primary color.