<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=706355809571598&amp;ev=PageView&amp;noscript=1">

Software Development Blog

The Belighted Blog

The latest in product development, product design, lean startup and SaaS.

Blog Feature

The Belighted Way

Mobile SaaS apps: should you go native or hybrid?

Most SaaS app founders realize they must have a mobile counterpart to their web application, because users expect functionality on their phones.

Read More

Blog Feature

The Belighted Way

The front-end: React vs Angular

To put together the front end of a web application, developers often start with an existing framework. React and Angular are the two most popular front-end frameworks available. Today we’ll talk a bit about each and which one we prefer. But first, let’s back up and clarify a few terms for the non-technical among us... What does “front end” mean? When we talk about front end, we’re talking about the parts of an app that users see and interact with. For example, when you book a place to stay on Airbnb, you are interacting with the front end of the app. The back end consists of things you don’t see but are required to make it work, like the server and databases. When developing the front end of a web or mobile app, your business will benefit from two disciplines: UI and UX. These work together closely, but the focus of each is different.

Read More

Power Checklist for New Sotware Products

Consider this your cheat sheet for developing your startup.

Blog Feature

The Belighted Way

Demystifying Ruby on Rails

Software development is an expensive part of the journey of a startup. Speed of development can make the difference between getting off the ground or crashing and burning. The technology stack you build your app with plays a big role in that equation. Today we’ll offer up the non-technical startup founder’s guide to our preferred programming language and framework for the server side when building an app: Ruby on Rails (RoR).

Read More

Blog Feature

The Belighted Way

The Belighted technology stack

Have you heard of AARRR? How about GRRRRR? We don’t mean the 2004 French movie. We’re talking about our technology stack. It might feel like developers are speaking a different language when you discuss your new product or app. We’ve said it before: It’s not necessary to have a technical background as the founder of a software startup. But there are some basics you should understand. Technology stack, or “tech stack,” refers to the collection of programs, frameworks, and coding languages developers use. These function together like a stack of sieves transforming data at each floor. All the sieves are specialized to handle the kind of data they receive and provide another kind of data to the next layer. Hence the term “stack.” The technology behind your new product can impact critical short-term factors like speed to market and project cost, as well as long-term factors like your ability to scale and ease of maintenance. If you’re considering working with Belighted to build your new product, you’ll want to know our preferred technologies and why we chose them.

Read More

Blog Feature

The Belighted Way

Speed: use market validation to fail faster

If you’re going to get something wrong, it’s better to find out fast. With market validation built into your product roadmap, you can find out where you’re wrong faster. And you will get plenty wrong. In three years, if you’re still around, your startup may look completely different from what you imagined. This post is the last of our three-part series demystifying startup failure. We talked first about the concept of speed in building your team. Then we dug into how focus can help you move faster. Today we’re going to look at the fundamental role market validation plays in speed.

Read More

Blog Feature

The Belighted Way

Speed: How focus helps a startup move quickly

Most startup founders know speed is important. But speed in the wrong direction may be worse than going too slow when it comes to developing a new software product.  Veteran startup CMO and former marketing head of Google play Patrick 'Mad' Mork tells how focusing on the wrong thing killed his startup: “When I was at GetJar in 2010, we had to rebuild a large part of the platform from scratch. We had grown too fast and had made a number of obvious mistakes when it came to scalability. We lost at least a full 12 months rebuilding our systems, when we should have been focusing on other changes that were happening [in] the market. That mistake, among others, eventually doomed the company (along with the $40M we had raised in VC funding).” In the first of this three-part series demystifying startup failure, I talked about the concept of speed when it comes to building your team. Today we’re going to dive into the concept of focus and how it relates to speed for a startup.

Read More