I'm a non-technical founder developing a karaoke mobile app. How I should architect my app in term of software/servers used and programming languages?

You can have a look at http://ekipa.co

Wow...what a big question...here's a few answers... The most important thing to know is that 90% of engineering management is culture management. If you build the right culture, then the engineers will manage themselves. So, do some web searches on engineering team culture and read those types of blog posts. Also, read this: http://algeri-wong.com/yishan/engineering-management.html. Additionally, you can read my blog, I've written quite a bit about engineering management (but I don't write as much as I used to): http://scottporad.com. I follow Hacker News regularly. Personally, I spend my time on the "new" page instead of the "most popular". I developed a deep understanding of Agile and Lean Startup methodologies. The key wasto understand them philosophically and strategically, as opposed to simply understanding them tactically. Once I understood them at their essential levels, the principles could be applied to all types of organizations. Another thing I've done is to identify other organizations that served as "role models" for my team. Then, I would follow their blogs, find the slides from when they speak at conferences, etc. I would look for companies with similar technology, that appeared to be leaders in their space. Of course, find yourself mentors with whom you can discuss your issues. Obviously, you can find those people here on Clarity. Finally, in Seattle, where I live, we have a Seattle CTO mailing list consisting of senior engineering managers from across a broad set of companies. Find the version in your city, and if doesn't exist, start one.

I hate to say it, but Google would have got you a much faster answer than this site. I just typed in "Software life cycle" into google, and there are many great articles.

I've been involved in several projects that hinged upon this question (generally start-ups or web+mobile apps), and it's not a clean or easy answer unfortunately! Plus every developer you talk to is going to try to sell you their services, but what you need is simply the truth! I'd suggest that you consider shifting your focus away from finding a best language. That sort of premise can eliminate options that are actually quite valid solutions. Keep in mind that any mobile app will require multiple languages working in harmony - all while used in a commercially consistent and standards-based manner. That's the part that determines your technical scalability! Almost every programming language can achieve this functionality with an experienced developer on your team. The best advice I can give you, is to consult with at least two people on this, and three if your app is os-specific. The most important insight will come from a "full stack" developer. One who's got a variety of enterprise experience, and can code at all levels of the stack. This person needs to have experience in leading a team of other developers, which forces the strategy of which technologies to use and why onto their plates daily. Secondly, you'll want to consult with a "front end" developer, who can tell you what's possible using advanced OOP JavaScript techniques (like Google's angular.js), because in an absurdly fast change over the past 3 years, much of the formerly back-end work has made it's way to the front-end, and is driven by JavaScript, predominantly JSON data, and awesome API's. The game has changed and the front-enders are the poor souls dealing with this rapid shift daily. To do this, they're also fantastic JavaScript programmers, which is a language that runs on all mobile devices and all browsers, too. Love it or hate it JavaScript is the most commonly used language in the world. Finally, if your app is OS-specific, you'll want to consult with a developer who works predominantly with the OS your app is built for. This person lets you know what's possible from the device POV, should know what stacks and JavaScript approaches can and can't be done on that OS, and how to leverage the resources of the device for your app as well as extend it's functionality. BONUS - loop back to the full stack developer to double-check the claims of the front-ender and the mobile developers. Always double check with your most senior programmer ;) All of these consults together in addition to your own research and due diligence will get you comfortable and allow you to navigate on this rather daunting but deeply important journey. There aren't any turn-key options. Instead it's a series of inter-connected modules driven by different languages, and all working in tandem. Every solution will have bugs, and no one group of technologies can do everything without proper developers. If you'd like to go further down the rabbit hole, then we should definitely set-up some time to speak. Otherwise, I wish you great luck in research and encourage you to learn as much as you can! :) It's going to seem hard, and might give you a headache here or there, but learn everything you can about how different technologies "talk" to each other, and then you will be able to build a map for keeping your app and business scalable regardless of the changing tides of technology!

I've always hired only ridiculously brilliant engineers and those that were either entrepreneurs or entrepreneurially minded (i.e. attended startup weekend, contributed to open source, blogged, etc). The best way to find them is to go to the events they attend. Typically it's developer meetups, open source or programming language oriented conferences, etc. To add a heightened filter, maybe only entrepreneurial oriented events like Business as Software, StartupSchool, or StartupDrinks. Also, using Angel.co to find companies that were once listed, but didn't raise or seem to have "Sunsetted" might be a good strategy. The question I always ask myself when I'm about to do sourcing for talent, or marketing is: 1) Who do I want, or what are examples of those people in the real world? 2) What places do they go/hangout, tools do they use, news sources they read, etc? Be strict with your filters and you should find some candidates... the hard part is convincing them that your project is more interesting then their current job/project/ideas/company/etc - cause these people typically have many options for work.