For very complex projects, I like to try to group the layout files together so that activity files, fragment
files, adapter files and include files are all together. Developers working on an activity or fragment can immediately find the file that they need to change. I do this by placing a key at the front of a file. Doesn't matter what the key is just as long as it makes sense. I typically make the activity files "views" and prepend a vi_ to their file names.Why? Eclipse will display the files alphabetically and since they files are not modified frequently, I want them at the bottom of the list and out of the way. Same goes for adapter template files.
Here's what I use:
1, Container/Activity Files
Name container files the same as activity where possible. In this case I’ve named them vi_{ACTIVITYNAME}_container_portrait.xml and vi_{ACTIVITYNAME}_container.xml (for horizontal mode) I named them vi_* so that they end up towards the bottom of the directory since we won’t be touching them much and they’re more out of the way then.
2. Fragments
In the example above, I named the fragment xmls, {activityname}.xml but we might want to call them fr_{ACTIVITYNAME}_top.xml, fr_{ACTIVITYNAME}_bottom.xml etc
3. Include files for things like common headers I call inc_{FILEPURPOSE}.xml for example inc_topnav.xml
4. Adapter list item files (I don’t see any in the screen shot) I would call li_{purpose}.xml Purpose is generally related to the adapter name. For example, an adapter that shows a list of products would be called ProductsAdapter.java with the list item being li_productsadapter.xml
