A related thing I often raise, when someone asks if there is a tutorial for <detailed description of app>, is that there is not a tutorial for everything. I think there is a reason tutorials generally stick to simple, recognisable concepts: you don't want readers to be confused about what the app does, and so familiar systems are a good starting point.
The usual things like a blog, a forum, or a shop, are meant to teach generalisable skills, so you can see what technique is appropriate for which situation. Once you've understood database design, or HTTP, or the event model of your windowing system, or whatever, you can start to branch out and modify things on your own.
Don't write tutorials off though - they are a great starting point. If you want more of a challenge, take something you've built in a tutorial and add a feature that isn't described - not as scary as building a new app but a good jump towards that.