i've been pretty excited about this since i first heard of android and what they were trying to do with it. now it's finally here and it actually looks like it won't be a major disappointment. actually, if my logic works out it should be a direct competitor to the iphone. how can anything compete with the iphone and it's already huge lead in the consumer smart-phone market? let me explain.
when it comes to technology i have two main theories about future areas:
1. it's all about being open.
- the more freedom you give developers, the better a product you will have
2. if you can make money by giving it away for free you force your competitors to do the same
some will say, "look at symbian, they tried this and aren't anywhere near the iphone." except this is a different time than the old market. just last month my sister, a poor college student, got a blackberry pearl with internet. you couldn't say that about any average consumer 5 years ago. the new internet phone market is taking over.
but "how can android ever compete with the iphone?" well android has a few, very key, advantages that the iphone doesn't:
1. android isn't a phone, it's a platform
- yes, the G1 may not have the same features that the iphone does, but another phone will
- android can be run on cheaper phones, so almost anyone who can purchase a phone should be able to eventuall afford a phone that runs android. this would let anyone buy marketplace apps(i.e. app store) that their phone can utilize
2. android isn't locked down to one carrier.
- soon everyone will have access to an android phone, maybe even At&t folk
3. android is an open java platform
- android developers have millions of java applications to choose from they can almost copy over to make new android apps
- android gives developers much more access to their architecture giving them the ability to make better applications
i could go on, but i think those alone will give android enough juice to be a major competitor. don't get me wrong, the iphone is great for people who want everything simple and to 'just work' where android phones may not be so simple. but if you want to truely 'own' your phone, have a ton of options for produtivity apps android is the way to go.
either way, both of these phones are making carriers FINALLY change the way they allow access on their networks. it's a change we as consumers have been deserved for a long time and are finally starting to see being realized.
Wednesday, September 24, 2008
Friday, September 5, 2008
javascript module pattern...it's what we all should be using
those that know me in the tech world know that i'm an avid ajax developer. i'm as obsessed as i can be about being on the cusp of new tech. and get all giddy when i see any new functionality that i can integrate into my toolbox. that being said, i recently made the switch from prototype to jquery.
there's 3 major reasons for my switch:
1.) jquery is smaller
2.) jquery is faster
3.) jquery has more of a plugin base(prototype doesn't even have plugins) and there are way more things made with jquery.
being an avid prototype user i was heavy into using it's built in classes. a prototypejs class is basically a json object that calls an initialization function when initialized. when i switched from prototytpe to jquery, that had to change.
i read into the jquery forums to see what other people were using, and i found that the most advanced plugins and best implemenations that i could find were using the module pattern.
i started using this in a new site with jquery and i have to say, it's a lot nicer way to program js. it changes the scope so you don't have to worry about binding all of your functions. also, as i read on another site, i'm using two variables for public and private objects (pub and pri) that i prefix onto anything. then all i have to do is return pub and it's all set.
i do have to worry about calling my init function now, but that's ok. 6 extra characters is worth it. check out the basic explaination here:
http://yuiblog.com/blog/2007/06/12/module-pattern/
there's 3 major reasons for my switch:
1.) jquery is smaller
2.) jquery is faster
3.) jquery has more of a plugin base(prototype doesn't even have plugins) and there are way more things made with jquery.
being an avid prototype user i was heavy into using it's built in classes. a prototypejs class is basically a json object that calls an initialization function when initialized. when i switched from prototytpe to jquery, that had to change.
i read into the jquery forums to see what other people were using, and i found that the most advanced plugins and best implemenations that i could find were using the module pattern.
i started using this in a new site with jquery and i have to say, it's a lot nicer way to program js. it changes the scope so you don't have to worry about binding all of your functions. also, as i read on another site, i'm using two variables for public and private objects (pub and pri) that i prefix onto anything. then all i have to do is return pub and it's all set.
i do have to worry about calling my init function now, but that's ok. 6 extra characters is worth it. check out the basic explaination here:
http://yuiblog.com/blog/2007/06/12/module-pattern/
Subscribe to:
Comments (Atom)
