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.
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.
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!
We are a Web development service provider. We design and develop our own website, as a proof to clients what we can do. But sometimes, when it comes to your own website, you tend to put everything you know in there - make it the best one you did. As a result, you take too much time doing it, instead of others doing it for you. So if you have a specific launch date, develop your own website within that period only. Otherwise, hire someone to deliver your website at your desired deadline.
It is also not a "document" for me, a "form" (that a non-programmer may use to build their own custom online forms). So I guess, providing a map of flow of operations/commands will be helpful to tell the clients where Dokuments will play in their business/personal workflow. Good luck!
I would say, it depends on the app you'd build and the toolkit you'd need. For your web-based app for a financial enterprise, you’d only need knowledge/skills on database/SQL, HTML+CSS, and front/back-end programming (i.e., JavaScript, PHP, VB.NET). Here you’d only need reference materials, as you can easily find how to develop the modules you’d need.
However, imagine what you could miss? During the design phase, diagrams, (R)DBMS, OOP, algorithms and software engineering skills are some of the vital CS fundamentals that will eventualy result to the overall quality of your app. You may be able to develop a complete app, but you may not be able to know if it’s the best implementation. While testing your app, you might find some CS concepts (i.e., data structures, searching, Big Oh) relevant along the way, to enhance the processes maybe. Yes you could study these topics by your self, but you might be more effective if these are already in your armory before jumping to the job. Like when you’re programming, an OOP approach might be a better approach as early as the initial coding, rather than convert to it after launch. Or you might learn that you could offer real-time collaboration using other networking/Internet technologies.
Yes you don’t need a CS degree, but let me suggest that you scan the CS topics before you start designing your app. Someone who has a CS background may be able to forsee all posible problems and solutions to its system right after the inception of the idea, while someone who’s not, must explore all possibilities and validate them in each step he/she would take. I’m not saying that you cannot build a good app, I just hope that you won’t miss something. Good luck Sir!