planning-poker-teams / planning-poker-ios Goto Github PK

A lot of people download the app and get confused about how it works. When starting the app for the very first time there should be a small intro screen.

The following topic could be part of it:

• What is planning poker
• How does this app work

• check out dribbble for inspiration
• define a set of colours to be used (light and dark mode)
• add codecentric card deck images (see https://gitlab.codecentric.de/codecentric/cc-planning-poker/tree/master/assets)

It is necessary to generate screenshots of the app for certain device types. Fastlane supports generating those automatically based on app UI tests.

Making the Most of Your Product Page
Screenshot requirements
Screenshots with fastlane

• set up UI tests
• define "checkpoints" to take screenshots
• adjust fastlane config to upload those screenshots to the app store

When running into a "Catsensus" the cached cat image is used. It should load a new cat every time.

👉 See related issue at https://github.com/c-st/planning-poker-web/issues/15

Due to legal compliance reasons we need to do the following:

• Add link to data protection declaration in AppStore description page
• Show terms of use on first app launch (this could be combined with https://github.com/c-st/planning-poker-ios/issues/14). Without agreeing to our terms the user should not be able to use the app
• Make terms of use accessible after first launch (tbd - maybe restart onboarding screen?)

In addition to screenshots (#3 ) it is necessary to write some fancy words in multiple languages about the app. This can also be done with fastlane and is already configured. See https://github.com/c-st/planning-poker-ios/tree/master/PlanningPoker/fastlane/metadata.

Currently spectator mode (read-only) is missing. This feature affects the following areas:

• when joining add an option to join as a spectator (in that case a query parameter has to be added to the connection URL)
• participants who are spectators should be displayed differently

Reproduce:

• join a room with other participants
• leave the app by going to home screen
• other participants leave room
• return to app

-> other participants who left the room are still displayed

Possible solution:
When applicationDidBecomeActive is triggered, re-join the room to receive the latest participants. Probably also broadcast the estimation again.

Cat mode is currently always turned on. Add a toggle to change that 😿. It should be enabled by default (of course ;)).

We should (non-annoyingly) ask for reviews or star-ratings in a prompt. For example showing the consensus cats for the first time could trigger the prompt.

See SKStoreReviewController from StoreKit:
https://developer.apple.com/documentation/storekit/skstorereviewcontroller

best practices: https://developer.apple.com/documentation/storekit/skstorereviewcontroller/requesting_app_store_reviews

Cards from the center of the deck barely rotate, those from the sides of the deck go crazy...

Also: initially, the card ??? is hidden until dragging another card is started.

Improve display of other estimators.

• Choose a supported CI system (Github Actions, CircleCI, ... ?) to run fastlane
• Build app in pipeline using fastlane
• Also run fastlane beta in pipeline (only on master branch) in order to push to TestFlight

In horizontal orientation interface elements are covered due to missing vertical space. They should be realigned (or put in a scrollView) to support landscape layout.

For now only "portrait" orientation is enabled (Targets/Planning Poker/General/Deployment Info/Device Orientation).

Use new websocket endpoint api.planningpoker.cc (no query parameters required)

Breaking changes:

• joining a room is now done by sending a joinRoom message after connecting to the websocket endpoint
• disconnection however still happens by closing the websocket connection

Keep in mind:

• API gateway has idle timeout of 10 minutes
• duplicate names are supported according to the API (uniqueness is not enforced yet), make sure that everything works when playing with identical names
• when releasing the app update in the App Store the new API is used. Make sure that frontend is also switched over to the new API.