Taking the current Android build we have the following info:
App name
Goryon
Package name
social.yarn.goryon
App version
1.0.5
Build number
65
I'm proposing the following changes:
App name
Yarn.social or just Yarn
Package name
social.yarn.app
App version
Keep the 1.0.x convention until we start to add more features and then jumping to 1.1.0
Build number
Perhaps going with 66 and such, or skipping to 70
I agree on renaming/rebranding the Mobile App.
Taking the current Android build we have the following info:
```
App name
Goryon
Package name
social.yarn.goryon
App version
1.0.5
Build number
65
```
I'm proposing the following changes:
```
App name
Yarn.social or just Yarn
Package name
social.yarn.app
App version
Keep the 1.0.x convention until we start to add more features and then jumping to 1.1.0
Build number
Perhaps going with 66 and such, or skipping to 70
```
And regarding the icon, I attach a draft (slightly based on https://developer.android.com/develop/ui/views/launch/icon_design_adaptive)
App name, Package name and icons were changed. Any reference to Goryon I found was changed to Yarn.social.
The App version and Build number has not changed yet.
Notes
App Icons were automatically created with the tool flutter_launcher_icons
There are a few remaining icons of Goryon not replaced by that tool. It seems they are for an older build process. I'll need to double check if we can delete those, and that only the Yarn icon is being included in the build.
It was tested locally on a Debug APK.
I don't know the process to notify of progress on this issue, (if you have some guide, it would be amazing)
I submitted this Pull Request
https://git.mills.io/yarnsocial/app/pulls/139
With the following changes:
> App name, Package name and icons were changed. Any reference to Goryon I found was changed to Yarn.social.
> The App version and Build number has not changed yet.
**Notes**
- App Icons were automatically created with the tool `flutter_launcher_icons`
There are a few remaining icons of Goryon not replaced by that tool. It seems they are for an older build process. I'll need to double check if we can delete those, and that only the Yarn icon is being included in the build.
- It was tested locally on a Debug APK.
@pratikbaid3 I think we've already done this work. I think @eaplmx did most of the work here already. The App looks to be called "Yarn.social" now and has the right App Icon / Logo.
What else do we need to do here? Eventually rename the App Bundle ID? (If so, I don't think we need to do this now, as we should wait for me to get #146 done)
@pratikbaid3 I _think_ we've already done this work. I think @eaplmx did most of the work here already. The App looks to be called "Yarn.social" now and has the right App Icon / Logo.
What else do we need to do here? Eventually rename the App Bundle ID? (If so, I don't think we need to do this now, as we should wait for me to get #146 done)
See: https://twtxt.net/twt/z3aysjq
I agree on renaming/rebranding the Mobile App.
Taking the current Android build we have the following info:
I'm proposing the following changes:
And regarding the icon, I attach a draft (slightly based on https://developer.android.com/develop/ui/views/launch/icon_design_adaptive)
Sounds perfect 👌
I don't know the process to notify of progress on this issue, (if you have some guide, it would be amazing)
I submitted this Pull Request
#139
With the following changes:
Notes
App Icons were automatically created with the tool
flutter_launcher_iconsThere are a few remaining icons of Goryon not replaced by that tool. It seems they are for an older build process. I'll need to double check if we can delete those, and that only the Yarn icon is being included in the build.
It was tested locally on a Debug APK.
@eaplmx I will check the branch out and do some testing 👌
@pratikbaid3 I think we've already done this work. I think @eaplmx did most of the work here already. The App looks to be called "Yarn.social" now and has the right App Icon / Logo.
What else do we need to do here? Eventually rename the App Bundle ID? (If so, I don't think we need to do this now, as we should wait for me to get #146 done)
I'm going to close this as "Done".