What are some suggestions of good online calendars that I can use?

Being a freelance developer for the last 10 years or so, I have seen and used almost every project management software you can think of, open-source and closed, and I have found that the "best bug tracking tool" completely depends on your process. I employ and direct teams in an Agile process that involves loose story-based requirements with point-based estimates, two-week cycles of iterative development, planning and retrospective sessions, and look-ahead and show-and-tell meetings with the stakeholders. It's important to me, then, that my tools have a method of capturing all those pieces with as much detail as I need but no more. On projects, I've successfully used Pivotal Tracker, Unfuddle, Redmine, Codebase HQ, Basecamp, Trello, and many others. I usually recommend people to Trello for light, agile management; it's essentially a digitized version of sticky notes and swim lanes. If your team actually needs a full-featured ticketing system, see Redmine (Rails), Trac (Python), or Mantis (PHP), depending on your language preference. Hosting a version of these yourself is fairly trivial, and numerous options exist for cheap or free hosted versions. For something in the middle, Github Issues is a good fit and the open-source clone GitLab.org replicates most of those features nicely. However, if you're looking for a hosted version, you're probably looking to offload that tricky "backup" thingy, and in that case, how important is your data? How proprietary? What's your business model? If you're working on an open-source project, Github will give your team a free account with private repos, issues, wikis, and the like. If you're okay with your project being "readable by all", public projects on Pivotal are still free. I'm mostly a consultant these days, leading small groups of junior or intermediate developers into a more productive, more mature, fully operational teams of senior software developers. One of the first things I teach folks is how to use a project management system... and why! It'll save your bacon if it's simple, effective, and reliable. With a few minutes of discussion about your project, I can probably help you select the right tool and service for your team. Let me know if I can help with that. Best of luck!

If you are aiming on iOS and Android with Windows Phone 7/8 as a plus you should use C# as the language and Xamarin Studio as the IDE/Framework. You may also choose to use Visual Studio on Windows as an option. Take a look on their website: http://www.xamarin.com Even Microsoft is using Xamarin to build iOS applications and they have over 400k developers using it. Your application will be native (compiled to the platform you choose) and you are able to use all the native libraries, widgets and UI parts. You will need a cross-platform architecture to be able to reuse code among platforms and using Xamarin you may be able to reuse more than 50-60% of your C# code among platforms. This solution may render the same experience on the devices as on the website, but it enables your applications to deliver much more performance and features than any HTML5 solution. Facebook went from HTML5 to native applications due to performance and user experience limitations (gestures and other platform features are not present using HTML5).

The best way to build an MVP for any SaaS product is to create a landing page that looks like a real product. Here's an example of one I built. http://www.happiily.com In this case, it advertises the primary features of the product and invites people to sign-up. When they do, they are asked for information which qualifies the person and then sends me an email. I built this quickly and very inexpensively and started getting inbound leads from it shortly thereafter. I got on the phone with each person who signed-up and explained the features I wanted to build and was able to do a lot of customer learning based on that. Happy to talk to you in a call if you'd like to talk more about customer development with SaaS products.

Having gone through this multiple times either in new startups or for side projects, here is how I would approach turning your idea into an app. 1. Defining the Minimum Viable Product Your first goal with any new idea should be about proving the idea and finding a market that wants the app you want to build. Achieving that quickly is probably one of the most important thing. To achieve that, you will need to write the specifications that will constitute your MVP. The MVP is basically the simplest expression of your idea to prove it. This step should not cost you much as you can do this on your own. 2. Design the app Before starting any development work, I would suggest you work with a good UX/UI designer to create wireframes and mockups of the app based on the specifications you came up with in step 1. You can find good designers in meetups & hackathons or on website like Dribbble or 99designs. If you want to reduce your costs, you can give shares in the project to the designer. Otherwise, it really depend on the size of the MVP but I would say it will probably cost between $5K-$10K. 3. Develop the app Once you have the specifications and the design of the app, you now need to find a good developer that will build it. Again, you can find good developers in meetups & hackathons or on sites like Github. If you want to reduce your costs, you can give shares in the project to the developer. Otherwise, it really depend on the size of the MVP but I would say it will probably cost between $10K-$25K. For this part however, I would recommend the developer becomes part of the project as his engagement will most likely be higher. 4. Test the app This step is not only about making sure the app is bug free, it's also making sure the app does what was intended in the specifications. To test the app, you can use platforms like BrowserStack or SauceLabs which gives you access to multiple devices/browsers. You can do this step on your own so the cost will be for the subscription to the test platform which would be around $100/month. Hope this helps and good luck with your project.

It depends a lot of in the skill sets and experience of both people but in most cases the ux designer should be controlling the developer pretty heavily in order to make sure his ideas come through properly. The UX designer may just need to work on his approach so people don't feel bossed around and more like they are working together. In an ideal world, there would be a project manager who makes sure everything is communicated well and keeps the dynamic feeling great.