Little Apps or More Modules in the Core Product

IMG_2862
Image by alphabetjenn via Flickr

Sometimes we get the urge to build a little app on the side to solve a certain problem that isn’t as core to our main product (like billing). Fight the desire, we must. Building a small app outside the core product introduces a host of challenges like:

  • The fresh excitement to build an app from scratch wears off when no one wants to maintain it on a day-to-day basis
  • Testing and QA won’t be as rigorous due to higher priorities
  • Interface changes won’t be implemented consistently due to the separate code base
  • Server monitoring and administration infrastructure won’t be as thorough due to unique aspects of the architecture that are different from the main app

My recommendation is to avoid making little apps when at all possible as maintenance of them becomes a serious challenge. Unfortunately, they won’t be given the necessary on-going attention.
What else? What other thoughts do you have on making little apps vs more modules in the core product?

Comments

One response to “Little Apps or More Modules in the Core Product”

  1. Jesse Lingo Avatar
    Jesse Lingo

    Timely post for us- we just had to build a little webapp in prep for our release, and are considering turning it into an app on the side.

    I think we’re going to go ahead with it, mainly because its dead simple and we could easily make a little money on the side. The other consideration is that it gives tech media an extra motivation to cover us. That said, your points are good and we’ll need to talk them over. I’ll let you know how it goes!

Leave a reply to Jesse Lingo Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.