search

MobileChromeApps / chrome-app-developer-tool

Mirror of Apache Cordova app harness
Other
202 stars 33 forks source link

Misleading icon #48

Closed wernight closed 9 years ago

wernight commented 9 years ago

CADT is supposed to work with Chrome Dev Editor (CDE) but its icon looks like Chrome Apps & Extensions Developer which is unrelated (but also from Google).

mmocny commented 9 years ago

Indeed. By design (sadly).

TLDR; naming is hard, and since both are developer tools that are supposed to help you develop apps (or extensions), we decided to share.

We always try to augment the name by saying CADT for Mobile in our docs, but its confusing for many people.

I'll leave this issue open (wish we had a WTF tag ;) so we can at least update the icon with a little "mobile" device or something.

wernight commented 9 years ago

For the naming is see on the home page https://github.com/MobileChromeApps/chrome-app-developer-tool : "Th Chrome App Developer Tool for Mobile (CADT)" (not CADT for Mobile). Name I think is fine. Much clearer than "cca"/Chrome Apps for Mobile/mobile-chrome-apps/... Whatever name is fine, as long as it's short and unique enough, and especially visible as "the" name. Else you don't know what to search in Google. Ok that's outside this bug...

Just wondering why not use the icon of CDE? It looks like CDE/CCA/CADT work together.

mwoghiren commented 9 years ago

Chrome App Developer Tool for Mobile can be used without CDE (ie. using cca push). Because of this, it would be confusing if CADT and CDE had the same icon.

wernight commented 9 years ago

You could make it like a product suite, with a version for Chrome App, a version for command-line, etc.

mmocny commented 9 years ago

Valuable insights, but I don't think we will touch this any further for now.

I think our vision for the future is to move much of the CADT (for mobile) functionality into a single cordova plugin. Functionally, CADT would remain the same as it is.

But for cca apps, instead of using the CADT companion app, you would instead always build your own application shell, but in "debug mode", with support for asset-push, live-reload, etc. This would allow you to actually test services like gcm and payments, and use cloud apis tied to the application packageId. It would also be more clear how to go from debugging to deploying to the store.

So, the workflows would be:

Once we have this, we can consider re-branding CADT if it really becomes just a CDE companion.