Method Beta General Q & A

Re: Best Practice for App Naming Convention for Developers

mahlonf — Tue, 04 Nov 2014 20:40:50 GMT

Thanks!

That gives me what I need for now. I'm assuming we will be discussing that in more detail in the advanced track of the retreat.

Re: Best Practice for App Naming Convention for Developers

Method_Michael — Tue, 04 Nov 2014 19:24:46 GMT

Hey Mahlon-

As it stands today app names have to be unique there cannot be 2 apps named routes or 2 apps named Invoices.

If we create an app called Routes as part of a App Pack and you already have an app in your account called Routes you will have to rename the app in your account to install the Routes app.

The same app can exist in multiple packs but it would just be shared by the packs it would not be a seperate version.

Best Practice for App Naming Convention for Developers

mahlonf — Tue, 04 Nov 2014 09:39:01 GMT

I realize this may be a more advanced question, but I thought I'd throw it out...

What happens if down the road I create a Method Pack for an industry specific need...assuming we can do that...call SalesWürks for example.

Within the pack is an app called Routes...

Then the client decides to install another pack that also has an app called Routes.

Would this create a conflict...? If so, as developers, what is the best practice for naming conventions to distinguish our apps from apps that may be installed from other developers.

Thanks!