I am looking for advice on how to approach ensuring our application is COPA compliant (Child Online Protection Act).

This sounds as a deja vu to me. I have been in a similar situation back in 2000, we could only solve the issue thanks to a good mediator. However every situation is different and hence your route to a solution might be different. It also depends where you are in the world that defines how an email and/or verbal agreement might be a sufficient ground for legal actions. I am not a lawyer and can not judge that.

Usually Programmers are only slow when they don't know how to solve a particular problem. So they will spend a lot of time researching and a lot of trial & errors to solve a problem. It is important that before you engage a programmer on a project, you break down the entire project into simple, easy to understand modules. Let him give you an estimate of how many hours he will require to complete each of the modules. Example: a typical site will have a login module, registration, My account, profile etc. So let him estimate how much he will require to do the login. You can go even detail here. (e.g. how much extra time if you were to implement Facebook/Twitter Login?). Once he start developing, track his progress closely and make sure he is following his given timeline. If he goes over his budgeted time on a module, talk with him and see what went wrong. It is often seen that they may be wasting their time on something very insignificant that you may have asked him to implement, but you can totally go by without it too. So by understanding what is taking longer time, you will be able to prioritise things better. You definitely need some tools to get this done. Google Spreadsheet or Excel works just fine. But if you don't mind spending a few bucks there are many agile project management tools that you might look into. Here is a list, google them all and sign up for trials: * AgileZen * Agile Bench * Assembla * AssiTrack * Blossom * Basecamp * Breeze * DoneDone * Eidos * Fogbugz * GreenHopper * Jugggla * Kanbanpad * Pivotal Tracker Or the reason why he is slow can be purely non-technical. Sometime your developer may don't share the same level of enthusiasm as you about the idea that you are working on. They often don't often see the "bigger picture" (since you don't share everything with them explicitly). If you can somehow get them excited about what he is a part of, it will work like a drug :) He will work day and night without questioning you. But you need to work equally as hard as him. The moment he sees that you are the boss and he is just the guy doing work for you -- his mentality will shift from being part of something to being the low paid developer. Ultimately its all about motivation and making him a part of your venture. After all he deserves it, if he is really playing a crucial role in the entire development.

I'll keep try to keep this answer brief, but there are several factors and nuances that can be discussed in more depth. Where you decide to incorporate partly depends on what your future goals are with your company. Companies that plan to seek venture capital or go public typically choose Delaware as the state of incorporation, and usually choose a C-Corp. Delaware has a very well developed body of law surrounding corporate governance and that provides comfort and more certainty to future VC investors. If you're not planning to seek VC money any time soon, an LLC is a smart decision because of the tax benefits it can provide to you as the owner. It sounds like you want to grow your company on your own without outside financing. If that's the case, I would recommend forming your LLC in California. Regarding California vs. Delaware, one benefit to forming your LLC in California is that you can avoid paying a registered agent fee which can cost anywhere from $100-200 a year. If you plan to seek venture capital down the road, you can reincorporate in Delaware.

If I was just starting out, I'd consider learning Meteor (https://www.meteor.com/). It's just entered version 1.0 and after working with it for a little less than a year I do have some issues with it but it still makes for a very solid framework that gets you up and running very fast. You would only need to learn Javascript, and you can slowly work your way towards nodejs from there (which Meteor is based on) if you want to, or you could get the basics down and focus on learning design if you prefer.

I developed and published mobile apps as an individual for several years, and only formed a corporation later as things grew and it made sense. As far as Apple's App Store and Google Play are concerned, you can register as an individual developer without having a corporation. I'd be happy to help further over a call if you have any additional questions. Best of luck with your mobile app!