# Difference between app.import and just including lib in bower.json

**URL:** <https://discuss.emberjs.com/t/difference-between-app-import-and-just-including-lib-in-bower-json/9036>\
**Category:** Uncategorized\
**Created:** [October 30, 2015, 3:36pm UTC](https://discuss.emberjs.com/t/difference-between-app-import-and-just-including-lib-in-bower-json/9036 "2015-10-30T15:36:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Max](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/andrew_max/32/11193_2.png) [@Andrew\_Max](https://discuss.emberjs.com/u/Andrew_Max)\
**Post date:** [October 30, 2015, 3:36pm UTC](https://discuss.emberjs.com/t/difference-between-app-import-and-just-including-lib-in-bower-json/9036/1 "2015-10-30T15:36:56Z")

</div>

In the `ember-cli-build.js` folder you are instructed to user app.import to include libs in the generated output files.

My question is: what is the practical difference between this and importing the same lib in a specific file? Is it just a matter of scope or are there other practical differences in how you will be able to interact with these dependencies?