The Wall Street Journal reports that Verizon may offer an iPhone to customers as soon as 2011 Q1. Would that not be awesome? But wait, we have been hearing this same song be sung ALL SUMMER. It might seems as if it will really happen this time, however. Back in June, MSNBC released a similar article claiming the same date.
What does this mean for Apple? Most analyst suspect that Apple feels like they are losing ground in wireless communication to Android-based phones. The WSJ article shows that over the past nine months, there are roughly only 2.5 millions more iPhones than Android-based phones. This number has been reduced significantly since Jan 2010 where the difference was nearly 10 million. Moving to Verizon, the wireless provider with the most subscribers, is a wise decision on Apple's part.
What does this mean for consumers and developers? For Verizon consumers, this means they will gain an option in the category of smartphones. I do not, however, expect to see a dramatic rise in sales of iPhones vs. Android-based phones. The reason being is the lack of specific hardware and ease of development of Android apps. The uptight nature of Apple and the iPhone AppStore makes developing applications and getting them published costly and slow. The openness of the Droid Market and the number of user-friendly development tools makes Android a clear winner.
Wall Street Journal Article
Friday, October 8, 2010
Tuesday, September 14, 2010
Android No Longer the Runt of the Litter
Don't say I didn't warn you. I have been telling developers that Android is the new iPhone iOS. This article explains why. And why shouldn't it be? It is based on a well-loved, easy-to-use programming language, Java. I, having developed some iPhone apps (obviously with Objective-C), am not sure why any sane programmer would want to write in it. I enjoy writing software using ANSI C but not when I am making software for an end-user. Then Apple takes a perfectly well-executed language (ANSI C) and makes a disorganized mess of it. Wow, anyway...Android is up and coming. If you have not explored the idea of developing for Android-based phones, now is the time.
Read more
Reuters: Google's Android to be world No. 2 in 2010: report
Read more
Reuters: Google's Android to be world No. 2 in 2010: report
Tuesday, August 31, 2010
HTML5 - Know it!
If you have not yet taken a look at what HTML5 is and how it is an improvement over the current version, you are about to miss the boat. Here is some additional browser functionality ushered in with HTML5 compliance:
- Local storage using Javascript (big deal!)
- New semantic tags, like <section> and <header>
- Built-in geolocation functionality
- Drawing canvas
- Enhanced form features
To learn more, pick up a copy of the book (below) or take a second to read through some of the following sites:
 |
| Available on Amazon! |
Monday, August 30, 2010
I Have Access to AppInventor!
I am excited to report that I have (after quite a few weeks) been granted access to AppInventor. As far as I understand, access to AppInventor is restricted to educators at this time. I imagine, however, that it will not be long before Google opens it up to all who are interested very soon. For those of you who cannot play with it, I will take you through some of the abilities it offers!
There are two parts to developing with AppInventor: the web-based layout editor and a locally run code editor. As I stated in my recent post, you do not actually have to know how to write software (using Java) to make applications. This is the neatest part of this product. All of the "programming" is handled using a drag-and-drop editor! No Java experience required.
 |
| Screenshot of the web-based layout editor (http://appinventor.googlelabs.com) |
 |
| Screenshot of the locally-run drag-and-drop code editor |
Read the official blog post for AppInventor's release.
.htaccess Trick to Redirect All Traffic
A neat article from a local Columbus developer on how to "take down" your site for updates using .htaccess.
Read the Article
Read the Article
Monday, July 26, 2010
3 Awesome APIs Everyone Should Know
These days, application programming interfaces (APIs) are ubiquitous. Without them, Web 2.0 would not be what it is. Developers would not have any means to hook into other web services and create useful mashups. The overall integration of content on the internet would be next to nothing. You would not be able to post a link to Facebook about a YouTube video (from YouTube) or update your status on Twitter from your iPhone. We rely on APIs heavily for much of what we do on the internet. Here is a brief overview of some neat APIs every developer should be aware of:
1. Facebook API
If you have not heard anything about Facebook's different APIs, you must have been living in a hole for the past few years. Facebook has become the de facto social integration tool. With over 500 million active users, Facebook has become an unstoppable force of content generation and user interaction. I have even heard some people say that Facebook is becoming the internet. The company has strategically infiltrated every corner of the internet with "Like" buttons and "Login with Facebook" buttons. This is not an API that any developer can continue to ignore. Seriously. It is "do or die".
2. GoWalla API
GoWalla.com's API is a location-based web service. It provides developers with a way to convert between latitude/longitude coordinates and nearby establishments. GoWalla really hit big once it was debuted at the SXSW conference in 2008. You give GoWalla a latitude, a longitude and a radius (in miles) and it returns a feast of nearby establishments in JSON. The reason why I like this API so much more than GoWalla's main competitor, foursquare.com, is the type of data GoWalla gives access to and the fact they use a REST approach.
3. Google Maps API
You can integrate a map of anywhere into anything now thanks to Google Maps. Yes, there are mapping APIs available (Bing and MapQuest). There are drawbacks and benefits to each. I have the most experience with Google Maps due to a project I worked on recently. The project required a robust map and the supplying service to allow many thousands of hits a day without incurring a cost (initially, at least). Bing's terms of service stated that the number of requests per day were closely monitored and highly restricted. MapQuest's API (see Documentation) was not flexible or stable enough to handle the complicated requests we were making from our service.
Google Maps API came out a strong contender and never disappointed. Google offers some extremely useful functionality and the service was very reliable.
1. Facebook API
If you have not heard anything about Facebook's different APIs, you must have been living in a hole for the past few years. Facebook has become the de facto social integration tool. With over 500 million active users, Facebook has become an unstoppable force of content generation and user interaction. I have even heard some people say that Facebook is becoming the internet. The company has strategically infiltrated every corner of the internet with "Like" buttons and "Login with Facebook" buttons. This is not an API that any developer can continue to ignore. Seriously. It is "do or die".
2. GoWalla API
GoWalla.com's API is a location-based web service. It provides developers with a way to convert between latitude/longitude coordinates and nearby establishments. GoWalla really hit big once it was debuted at the SXSW conference in 2008. You give GoWalla a latitude, a longitude and a radius (in miles) and it returns a feast of nearby establishments in JSON. The reason why I like this API so much more than GoWalla's main competitor, foursquare.com, is the type of data GoWalla gives access to and the fact they use a REST approach.
- GoWalla API Documentation
- Get an API Key
- Test out the API (without writing any code!)
3. Google Maps API
You can integrate a map of anywhere into anything now thanks to Google Maps. Yes, there are mapping APIs available (Bing and MapQuest). There are drawbacks and benefits to each. I have the most experience with Google Maps due to a project I worked on recently. The project required a robust map and the supplying service to allow many thousands of hits a day without incurring a cost (initially, at least). Bing's terms of service stated that the number of requests per day were closely monitored and highly restricted. MapQuest's API (see Documentation) was not flexible or stable enough to handle the complicated requests we were making from our service.
Google Maps API came out a strong contender and never disappointed. Google offers some extremely useful functionality and the service was very reliable.
Monday, July 12, 2010
Now Anyone Can Make Android Apps
A new tool from Google, named App Inventor for Android, promises to make developing applications for Google's Android platform easier than ever. App Inventor provides the user with a graphical approach to constructing apps.
Traditional development normally entails the Eclipse IDE, the Android SDK, and a lot of Java code. With App Inventor, you do not have to worry about any of this; you do not even need to be a developer. Most of the time, when an organization abstracts away all of the complexities of the product, it also inherently reduces its functionality. This is not the case with App Inventor as it still gives the user access to the device's GPS, phone features and camera.
App Inventor is built off of MIT's Java Open Blocks, a framework for visually representing Java code. This is the bit of the software that allows non-programmers to use it. Currently, this tool is only available to educators. If you qualify, I highly recommend checking it out and letting me know what you think!
Traditional development normally entails the Eclipse IDE, the Android SDK, and a lot of Java code. With App Inventor, you do not have to worry about any of this; you do not even need to be a developer. Most of the time, when an organization abstracts away all of the complexities of the product, it also inherently reduces its functionality. This is not the case with App Inventor as it still gives the user access to the device's GPS, phone features and camera.
App Inventor is built off of MIT's Java Open Blocks, a framework for visually representing Java code. This is the bit of the software that allows non-programmers to use it. Currently, this tool is only available to educators. If you qualify, I highly recommend checking it out and letting me know what you think!
Subscribe to:
Posts (Atom)