I've been debating how to respond to this paragraph for 3 weeks, since the integration / fragmentation between IP.Board and IP.Gallery is truly a perplexing problem for me. You bring up some questions that I'd like to address, even if I can only begin to scratch the surface.
For my particular community, I genuinely don't have a good reason as to why I still use image-only forums AND still offer IP.Gallery. I actually have duplicate content areas for TWO subjects in both IP.Board and IP.Gallery (yes, it drives me crazy), and it really just depends upon the uploader where he wants to be (which is why I'm a fan of seamless integration either direction to show media).
Some general observations, in no particular order:
In general, the forum tends to be the main 'hang out' area with more activity, so it makes sense to offer space there first. You just don't get the same feeling of 'activity' in IP.Gallery, so members are naturally more attracted to the forums.
Viewing gallery images is more of a solo activity.
Forums are great for progressing image topics. where new updates are posted in new replies.
Galleries are great for a curated showcase.
My personal difficulty with the enormity of this question - how to consume, view, and share content in a multi-app platform - is how you can change your interaction with the same content through multiple perspectives. For example, you can interact by publishing module:
IP.Board -- with categories to publish about Content A, Content B
IP.Gallery -- with categories to publish about Content A, Content B
It's equally valid to interact by theme:
Content A -- with permission to publish to IP.Board, IP.Gallery
Content B -- with permission to publish to IP.Board, IP.Gallery
Ultimately though, I decided a long time ago I shouldn't force my members to choose one app or the other. IP.Board and IP.Gallery both equally valid places to upload, since they can both still serve the fundamental purpose of being an image container.
