Ionic application directory structure


#1

I have a few questions about ionic directory structure that I hope someone can shed more light on.

My current directory structure:

config.xml
ionic.project
/platforms

  • android
  • ios
    /www (where my application resides)


    I have a build script that applies some gulp tasks to files under /www and then copies only /www directory to a new directory /dist and called ‘ionic upload’ on it.
    I inadvertently left out all the rest of the directories to copy over to the new /dist directory including /platforms, config.xml and others. Why does ionic view app still work and have access to the plugins?
    Is there some default plugins that are installed by ionic view if it detects uploading of an app without /platforms and config.xml?

I would also like to know what is the recommend way to package an app that uses plugins for ionic view upload. If I want to have specific plugins and configuration for android and ios bundled with my ionic view app, should I structure my app as follow?

config.xml
/platforms

  • android
  • ios
    /www

I noticed that /platforms/android/assets also contains a duplicate of /www files. which one will ionic view use? thanks much!


#2

The Ionic View app is an Ionic app with added plugins. Your app is inside of this app using the inAppBrowser plugin, and it has access to all of the same plugins. The full list of plugins supported can be found here: http://docs.ionic.io/v1.0/docs/view-usage

Here is a general overview of the Ionic View app: http://blog.ionic.io/view-app-is-alive/

I am not sure what you mean by packaging your app for an ionic view upload, but hopefully my previous statements cleared this up.