sesta / cellar Goto Github PK

投稿の「+」ボタンはお酒っぽいモチーフ（グラスに＋マークとか）にすると個性が出て良さそう
ローディングアニメーションもお酒っぽいモチーフ（グラスにお酒が注がれるとか）にすると個性が出て良さそう
お酒の種類によって入力したくなる情報が違うので要望が来そう（ワインの甘口辛口とか、ウィスキーやリニューアル系なら飲み方とか）
Tab Barのアイコンの大きさを統一するときれいにみえそう
- 数値的に同じでもイラストの密度によって見え方が変わります。その場合、ぼかしてみて一定の大きさに見えるかどうかを確認するとよいです
- 設定 > ホーム > タイムライン　の順で大きいです
ログ系サービスは褒めることが大事なので、投稿し終わったらテンションあがるアニメーションとかあるといいですね。10、50、100投稿で特別なアニメーションが出るとか

ローディングを追加

追加したいところ

投稿で画像を選択したとき
ユーザー登録の時

firebase_analytics を入れる

入れた方が良いっぽい
https://firebase.google.com/docs/flutter/setup?hl=ja#add_analytics

環境ごとにDBが切り替わるようにする

コレクションを切り替えるだけでひとまず良さそう

multi_image_picker を置き換える

flutter_wechat_assets_picker を使うべきらしい

参考: https://pub.dev/documentation/multi_image_picker/latest/

リジェクト対応

言われたこと

Guideline 4.0 - Design


We noticed an issue in your app that contributes to a lower quality user experience than Apple users expect:

- Your app's modal alerts are in English, but your app's primary language is Japanese. To help users understand why your app is requesting access to a specific feature, your app's modal alerts should be in the same language as the rest of your app.

Please remember that your purpose strings should:
- Explain how the app plans to use the data
- Be specific
- Provide an example

Next Steps

To resolve this issue, please revise your app to address all instances of this type of issue.

Resources

For information on improving and enhancing your app:

- Review the UI Design Dos and Don’ts for tips on fundamental design best practices.
- Watch the video The Ingredients of Great Apps to understand the basics of great apps.
- Watch the video iPhone and iPad User Interface Design for practical design tips.
- Watch iOS Development Videos to learn about programming and design tips.
- Review the iOS Human Interface Guidelines and ensure that your app's interface and design adhere to these guidelines.

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage


We noticed that your app requires users to register or log in to access features that are not account-based.

Next Steps

To resolve this issue, please revise your app to let users freely access your app’s non account-based features. 

Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app or required by law. 

You should allow users to freely access your app’s non account-based features. For example, an e-commerce app should let users browse store offerings and other features that are not account-based before being asked to register, or a restaurant app should allow users to explore the menu before placing an order. Registration must then only be required for account-specific features, such as saving items for future reference or placing an order.