Posts By Andrea Long

WordPress Plugins – The Starter Pack

WordPress is one of the most powerful content management systems for building websites. It’s intuitive dashboard and ability to add themes and templates are all strong features. But one thing that makes WordPress rise above the competition is the extensive library of plugins. I have yet to come to a point where I can’t find a plugin that does what I need. Whether you need responsive tabs, an impressive slider, social media feeds, or pop-up banners, there’s a plugin for almost any feature. When beginning a build, consider obtaining a “starter pack.” These are the three plugins that I’ve used the most often and have been the most helpful when starting to build a website.  1. Jetpack Cost: Free! The Jetpack plugin contains several features within itself, so I’ll just highlight my three personal favorites. The first feature I always activate is “Stats." This feature allows you to see how many people are visiting your site each day and how they ended up there. My next activation is “Subscriptions" which allows users to subscribe to your blog. The third feature is “Publicize” which allows you to automatically update your social feeds when new content is posted to your blog. 2. Custom Facebook Feed Cost: Free! The custom Facebook feed plugin does pretty much what it sounds like. It allows you to display a live Facebook feed on your website. There are paid features you can unlock, but with the free version you can control how many posts are shown in the feed, how often the plugin will check for updates, the size of the feed, and the placement of the page “Like” button. 3. Revolution Slider Cost: $19 The Revolution Slider plugin isn’t free, but it’s worth the $19 if you want a slider on your website. With Revolution Slider, you can easily control all animations, text placement, add videos, and most importantly, it makes sure your slider is responsive for every screen size. There are thousands and thousands of WordPress plugins, but these few can help you get a good start on your website build!

The Pros & Cons of CMS APP Builders

So you’ve decided you want to build your mobile application with a cross-platform solution. Now what? There is yet another decision to be made: Should you build your app with a CMS? Let’s first go over a quick definition of CMS, or content management system. What makes a CMS a CMS? First, there is usually more of a drag-and-drop feel than actual coding. An example may be dragging and dropping a text box component rather than coding ‘<input type="text"></input>’. Next, there will be some type of dashboard. And usually you will be able to create different permissions for various users of the dashboard. For example, you may want to allow someone to be able to sign on and change some text, but you may not want them to be able to edit the styling of the application so you would edit their permissions accordingly. Now, let’s take a look at the pros and cons of CMS app builders to help us answer the question we originally asked: Should you build your app with a CMS? Pros Code faster - CMS app builders allow you to build apps at lightning speed. I can build a complete app (ready to be submitted to the app stores) with a CMS builder within hours. The ease of drag-and-drop can save huge amounts of time and effort. Client customization - This pro comes along with the dashboard aspect of CMS builders. This comes in handy when you are offering customizable apps for clients. With a dashboard, you can create a login for the client and let them sign on to their application’s backend for simple text updates or adding a blog to a blog section, for example. Automatic updates - Getting an app through the App Store can be a frustrating process because of the length of time it takes to be approved. That’s not so bad for the initial submission, but waiting days for each update can be an issue if you have a client that is constantly wanting changes. Usually with CMS builders, you can automatically push 99% of updates (excluding splash screen or icon changes). Cons Costs money - One major con to using a CMS builder is that it is not free. Usually for a single app, it will cost about $50/month and will only stay live while you are paying the subscription. For reference, check out the pricing sheet for one of the top CMS builders here. You can easily see how this could get very expensive very fast with multiple apps. One thing to keep in mind is that if you know you will be creating multiple apps, most CMS solutions offer some type of affiliate program. This means you will be able to pay a higher monthly fee, but you will be able to create as many apps as you like. Less control - Sometimes with CMS builders, you lose 100% control of what you can do with your app. For example, they may only offer a set amount of templates you can use for a page. Most will offer a blank HTML template you can code yourself to help with this, but if you are trying to avoid hours spent coding then that doesn’t really solve your problem. So, what’s the answer? Of course, it depends. If money isn’t an issue and you want to be able to quickly create customizable apps, a CMS builder is most likely the way to go.

Coding Mobile Applications: To Go Native or Not

Before you begin coding a mobile application, there are several questions you need to answer. ● How many platforms am I going to support? ● Do I want to support a web app? ● Which platform should I start with? And the question we are going to look at in this blog post... ● Should I code natively or use a cross-platform method? First, let me give a quick definition of the two options. Native: This means you code for each platform. Meaning, you use XCode for iOS development, Android Studio for Android development, and so on. Cross-Platform: “Code once, run everywhere.” Write your code once, usually with HTML5/JavaScript, and run the application on multiple platforms. Now, let’s look at the question again: Should I code natively or use a cross-platform method? After reading the definitions, it may seem obvious that you would want to choose cross-platform because it only requires you to code your application once. But there’s another piece of information missing that you will need to make your decision. When you code cross-platform, there’s a chance you will miss some native functionality. For example, the overall look and feel of your application may not match the platform it is running on. Or, you may not be able to access all the features on say an iPhone camera or any other feature that is platform specific. With all of this in mind, the real answer to the question is: It depends. I know, that’s not the straightforward answer you were hoping for. But it is the correct answer. The way you code your mobile application depends on the way you want your application to be used. If you want to be able to access all of the platform specific features (or even just a few key ones), it is probably worth it to code natively. Or, if you want your application to have the look and feel of the platform it is running on, it is probably worth it to code natively. If the overall look and feel and platform specific features aren’t as important to you, you may want to look into some cross-platform solutions such as Appcelerator, but there are many solutions and it’s important that you find the right one for you. If you decide to go with cross-platform development, check out my next blog on cross-platform CMS builders.

Sign up for our blog updates!