This week was about research and training.
At the beginning of the week, I researched the new mobile application technology that I learned about last week. I found out how everything worked, how it compliled, what steps you had to take to start development as well as what hardware you needed to get started. I found some pretty instersting information...
It seems that if you use a product where you write one piece of code, it's going to do one of 2 things. The first is make a "custom" web browser for the OS that you compile for. This is the only code that's different between the different OS. Everything else would be written in HTML. You basically write an application to browse a website. If you are doing that, why not just make a mobile website? The only advantages to a mobile application in this sense would be push notifications and access to the camera.
The other method is for the program to be complied specifically for the OS. This requires more use of java when coding. The big problem with this method is that it doesn't perform as well as it can on each OS. If you write an application for a specific OS, the application should take advantages of all the OS's features and architecture. This isn't the case with method we learned about last week.
I also helped train our student worker. He's starting to learn SQL. I set him up a sandbox to play in that was created from an external table, then copied to a permanent one. The student worker can query and modify the table as he wishes. One quick command can restore the table to it's original condition.
No comments:
Post a Comment