jvickers

Swift is going to help iOS apps improve in quality and quantity - though some very bad quality Objective-C apps that would have been rejected into the store would be bad quality apps that are accepted into the store.

Your problem may be to do with using the App Store as the sales and advertising platform. If people find out about the app through the other means and purchase it in the app store, you don't have such a problem with your lack of visibility in the store.

I think there is a future for using apps as a mobile optimized interface for an online service, where there are other sales channels apart from the App Store.

When it comes to product discovery, people find out about products on the web at all sorts of times when they are not particularly browsing for an app. It helps if there is a decent web presence for them to see what the app does, and possibly use it in a web browser.

I think you should teach him to write HTML documents and then move onto JavaScript (including node.js) if he's ready.

Maybe a bit of C++ in a few years.

It looks very convenient for making some relatively simple web services (based on me not knowing much C++, others would get more mileage probably). It looks like the kind of C++ project of a moderately small size that's implementing something that I'm very familiar with already, so I think it will be useful to help me learn C++.

I have a couple of questions, and that is what is the reason for only having .h files with no .cpp files in the main part of the microframework? Did something force you to do it that way or was it done like that because you like that code structure?

I feel the same way about JavaScript, to some extent at least. I don't hate JavaScript - but I think that the web would be better if it moved towards making another language standard as well. I don't know which language would be best, Dart looks like a good candidate when it is more mature.