Archives for May 2011
review::WordPress for Android vs iPhone
Originally published on May 17th, 2011 this is an update to the original.
I recently installed the WordPress for Android app. While not something entirely new I figured it would be handy to have for some those short on the go type of posts. I also thought it would be worth a comparison to the WordPress for iPhone app which I have used from my iPodTouch on occasion.
So at this point I am attempting to work with the newest version of WordPress for iOS on my iPT. While I do not wish to condemn the app because it could very well be the device, I am going to say the at this moment I wish I were on my droid.
In either case both apps offer the same features and each version is tailored to respond as one would expect an app on the respective OS should. Likewise the look and feel are respective of each environment.
One issue on iOS seems to be the lack of or intermittent auto capitalization on the start of a new sentence which is rather annoying. This is something that I can work around but wish I didn’t have to.
Related articles
- Linux Today – WordPress for Android – A Blogger’s Dream App (lirax.wordpress.com)
- WordPress for Android: A Review (mobilejournalists.wordpress.com)
- WordPress for iPhone App Loaded with Stats Feature (shoutmeloud.com)
- This just in – Android to overtake Apple’s app market sooner than you think (marshallstanton.com)
- WordPress for Android powered devices (nightthought.wordpress.com)
rfc::Bash Library organization and contributions
Background: The Bash Library Project began as an accidental proof of concept to make writing system applications in bash easier. The original rudimentary functionality has evolved into a somewhat established standard.
Goal: To establish a standard by which all future blib development and user contributions should be set. In addition to make future development simpler and more straight forward.
Current State: The project has grow a bit in scope as a result of the constant development. There are new libraries being added to the base and a standardized installation system is in the works. What is particularly vexing is the development of end user libraries that are not part of the distributed base package. Refer to the following image which will aid in explaining the issue.
Discussion: The basic library is stored in /usr/local/lib/blib. The associated applications built using blib are arranged in their own library containers under /usr/local/lib. For instance examine the rotator application’s library in /usr/local/lib/rotator.
While this structure may work fine for small installations it is evident that is will not scale well. An alternative needs to be established to make projected growth easier. In addition the change should make support and expansion easier.
The development team is opening discussion to determine the path ahead for these end user libraries and accepting proposals for a new structure.
Proposal: Establish a /usr/local/blib/contrib directory to house each subsequent application’s library. This would mean relocating ‘rotator’ from the example above into the contrib folder. In addition to increase portability of blib overall they are proposing a blib.conf to reside in /usr/local/etc by default that will define certain basic installation specific entities.
Objective: To engage the community in the direction forward. Please use the comment stream to discuss options and offer counter proposals.
ABOUT THE AUTHOR: Mikel King has been a leader in the Information Technology Services field for over 20 years. He is currently the CEO of Olivent Technologies, a professional creative services partnership in NY. Additionally he is currently serving as the Secretary of the BSD Certification group as well as a Senior Editor for the BSD News Network.
Related Articles:
- Bash shell-scripting libraries ” Striving for greatness (dberkholz.com)
- Blib the bash library project (jafdip.com)
- release::Blib 1.1 and the diskcheck utility (jafdip.com)
To frak or not to frak…
To frak or not to frak that’s the question. Perhaps an even better question would be “Why the Frak not?”
Thanks to the success of recent SciFi blockbuster TV series like the Battlestar Galactica reboot and it’s short live Caprica spin off wonderful new vernacular nuggets have managed to perpetrate or vocabulary. Of these new terms FRAK is the most colorful and useful.
It is the most useful in that it can be used in place of the more derogatory FUCK without most of the latter terms sexual connotations. Just like the more offensive term it can also be used as every word in a sentence, but probably shouldn’t be. Obviously some of our older and more conservatively sensitive readers will still take exception to this new fangled term.
Perhaps you’ve noticed this site’s particular adoption of the word in it’s title. Yes the ‘F’ in jafdip is for frakkin which you should not does not have ‘g’ on the end. English formalities be damned.
So many of you readers are at the point of wondering what Frak does Frak actually mean? It is all a matter of context. I think Frak is best learned by example so here are a few.
1. What the frak = what the he’ll
2. Frakked up = messed up
3. Frak You = go to hell
4. Go Frak yourself = similar to #3
5. Frakkin unbelievable = beyond all comprehension
As you can see frak has become a useful tool to express certain phrases with the appropriate level of meaning all without the negative baggage of it’s less socially acceptable counterpart. Therefore I challenge you to come up with some more examples of frak in action and post them in the comment stream.
ABOUT THE AUTHOR: Mikel King has been a leader in the Information Technology Services field for over 20 years. He is currently the CEO of Olivent Technologies, a professional creative services partnership in NY. Additionally he is currently serving as the Secretary of the BSD Certification group as well as a Senior Editor for the BSD News Network.
Developer Diary: A look back, day 1
We would like to start by thanking Mikel for letting us guest blog on JAFDIP. We’ve talked with Mikel King a few times previously about our journey into location based services and his responses weren’t that different from many that we have heard before. When he put out a request for guest bloggers, we thought it was a great opportunity to discuss location based services and share our journey as a mobile developer. Maybe, we might also be able to answer the one question we hear most often, “What’s the point?”
Not quite a year ago, we decided to delve into the world of application development for Android phones. Grand visions of a level playing field where deep pockets and large development teams didn’t have an insurmountable advantage over the little guy drove us forward. We teamed up with another old friend to port some games we had done in the past for another platform. It was a great learning experience, but we found that the mobile market revenue models are still in their infancy. We tried several approaches, from alternate markets to integration with social gaming providers such as OpenFeint. It became clear to us that we would need to build content that could capitalize on micro transactions. We had the beginnings of a great design but the technology was not yet there to support it.
We re-grouped and decided to attack the revenue model first. From our experience, it appeared that consumers weren’t yet willing to spend a lot of money on individual mobile apps in the Android marketplace. Merchants, on the other hand, are very interested in promotion within this growing market. After many late night whiteboard sessions, we settled into the “deal of the day” space made popular by the likes of Groupon and Living Social. Coincidentally, we were friends with some local business owners who had used these social deal services before and regretted every part of it. They found many of the customers were one-time deal watchers and unlikely to turn into repeat customers. This, added to the fact that they were taking a loss on the highly discounted deals offered, made them uninterested in using similar services again. Some may call it a sign if you believe in that kind of thing, but this provided us the insight we needed. A bit of quick research showed that our business friends weren’t alone in their feelings on these services. After a few conversations with them, the pieces all started to fall into place.
Consumer loyalty is nothing new. It seems everyone has ten different supermarket key tags on their key chains and a punch card for the sixth sandwich free at a local sub shop. Or, if you are like us, you scanned the key tags into your phone and you have a handful of those sub shop punch cards sitting on your dresser, never with you when you’re actually getting lunch. This is where miPlaces was born. If we could make it easy for merchants to manage these loyalty programs, as well as make it easy for users to always have their “punch card” with them, we’d have a marriage made in heaven.
As it turned out, technology wasn’t the real challenge. The true issue was how were two tech guys going to convince merchants to offer great deals to users of our application. We felt it was critical that they offered something better than the run-of-the-mill deals that come in your mailbox every week. It needed to be something people would get excited about. However, we also wanted our approach to not overwhelm the merchants either. So after mapping out the application overview and detailing all of the powerful marketing tools we could provide to the merchants, we decided we needed to start small and grow into the end product. The key to our system was having the user’s mobile device know when you were at the merchant’s location, then having a secure way of counting and tracking the user visits for the merchant. We wanted to be able to reward loyal customers while generating foot traffic, and possible sales, for the merchants. Our system allows the merchants complete control over deals, redemption criteria and reward points accumulation. To get a foundation, we decided to build upon Facebook’s check in functionality, build a user base and develop reliable backend infrastructure while we get the rest of the tools in place.
Neither of us were big fans of “The Check In” and the idea actually seemed a little creepy. We tried all the existing check in apps and none of them appeared to be particularly great. We too were saying, “what’s the point?” But in the end, we’ve both become a little addicted to it. It’s more fun and less creepy than we expected. Even with mundane check ins we usually end with a handful of comments on our Facebook wall. You should give it a try, with our app or any of the other check in apps on the market. We’d love to hear what you think about the whole check in idea. Feel free to be honest as our feelings won’t be hurt. This isn’t our long term goal, just a fun little stop on the way.
Next Time: Wheels in Motion, over coming more obstacles.