zeroxsys

Check Scratch (MIT) out at http://scratch.mit.edu/

That's why I said "concepts" (not diploma), it's up to him how in-depth and/or hands-on he wants to go. But learning "how app's stuffs work" (the components of the app - design, code, controls/interactions, data) is the foundation on "building" one (that's because I don't believe a one-thingy app an app, like putting a photo on the screen, it gotta be 2 or more stuffs assembled together for me). If he just look inside an app, and he does not know what's the meaning of the "code" (module/library, object), programming, rebuilding/iterating, etc., he won't learn how and why it was built like that. Heck, he would't have any idea what he's looking at! Fundamental concepts, no matter how layman you can teach it to the kid, and having a "clear idea/plan/purpose" are essential before you send him to "just build stuff".

For a kid, drawing boxes of things he would like to put into his app, and seeing how he's going to put them together, is the best way to start an app, and the best way to identify the concepts/skills he needs to learn.

To get you started, I suggest you (or the kid's parents) tell him to draw how his app will look like, all screens (from the home screen to the scoreboard :)) on individual boxes, the size of his iPad/mobile device, then you guys cut them out. Then you link these screens/cut-outs with the navigation controls, for him to understand the flow, and the "big picture" of what's he's building.

These are of course, if you want him to build "something," not just practice/unfinished works that do nothing -- therefore does not contribute to the kid.

(I taught basic Photoshop to kids, 8-12 years old. They were able to compose cool graphics because they understood how to make bitmaps, shapes, texts, layers, blending and effects work together. I didn't underestimate them, they needed to know what the heck they're doing, so I really taught them those things, in the end, we had an unbelievable exhibit! :))

Advise him to learn the concepts on software engineering. Starting with software design using models/diagrams. It's a good way to visualize his app and the overall project. Then, he could move to coding using tutorials available on the web.

This pretty much gives guidance on the use of QR codes for any purpose.

Can you do Google App Engine in Netbeans?

Thank you so much @smoove, I totally forgot to do this on the server for my own sake! Well the reason is, I am really looking at a long-term solution, not just for this Japan address job.

This desktop app technique I am using now is more geared towards my clients who cannot do that command/code (you are recommending) themselves. I am looking at how to do this kind of migration and synchronization of local and online (MySQL) databases automatically (or at least with a single click by my clients). My clients may not even know how to do FTP; even if I provide them with manuals to the technical steps, they might find it difficult. That’s why I am building these VB.NET migration/synchronization utilities that do flat-file migration and local-to-online (Intranet-to-Internet) table synchronization so that they can accomplish the task on their own.

I can setup MySQL Replication but they will have problem with primary IDs. Aside from that, I don’t know other tools/technique out there that can do these migration and synchronization.

Yes, I am familiar with that, thank you @rick888.

I don't have a shell access to my client's shared server, so I can't do it using perl/bash. Yes, I'll try this with PHP instead.

Not using transaction, auto-commit.

Lint to "W3C Community Groups and Business Groups" proposal: http://www.w3.org/2010/12/community/

I'll check that out, thanks!

I agree, security in Web Socket must be robust/comprehensive in both ends. This post says so too: http://blog.kotowicz.net/2011/03/html5-websockets-security-n.... Thanks!

Hi! I can see that you're brave enough to be open about this weakness of yours here. That's a good trait of an entrepreneur, kudos!

As I see it, you don't want to "fail the first time you do it" - so you don't want your visitors to get negative initial impression simply because of some poorly written texts, which translate to being unprofessional. If you already have co-founders/teammates/friends, that have good communication skills, it's better to have them proof-read ALL your texts. Again, as I guess, you don't have one yet, that's why we are here.

If at this phase of your startup, you are willing to recruit co-founders/teammates to handle your communications, go ahead, it will make your product and your presentations (for your investors) language error free and better. However, I will not recommend that you choose them just for this purpose; your co-founders/teammates have to, primarily, help you build your product and your business – these two are the most important things about your startup.

So I strongly suggest that you focus on building your product and marketing/business strategies first, and not worry about English technicalities. Launch it, achieve your investment level, and setup your operations. Once you have the money, you can hire quality marketing personnel to help you make your texts smarter and effective. Good luck!