How to do agile prototyping using static pages to reduce development time

Captain's log, stardate d187.y37/AB

Launching a product is a battle against time. Nowadays, immediacy is required from every company because if you don't launch what I need, someone else will.

Some months ago, we published a blog entry about how we help our clients to reduce their time to market because we know that both entrepreneurs with their startups, big companies, and corporations need to launch fast to start gaining users and collecting data.

In this blog entry, we will give you more technical insight on how we prototype using static pages at MarsBased.

How we created our own frontend framework: MarsMan (and why)

Captain's log, stardate d164.y37/AB

2016 was a really challenging year for MarsBased. Throughout the entire year, we worked on about 16 different projects, and even though I joined as a full-time employee in June, I've been involved in most of them in the design, UX and frontend development phases.

Switching projects isn't always easy, especially when dealing with different clients who have different tech stacks and different libraries in every project, or even very diverse visual guidelines.

Luckily enough, we came up with the idea to standardise the visual elements we're using throughout all our projects and grouped them in a library of our own: MarsMan.

What is the best Ruby on Rails CMS?

Captain's log, stardate d39.y37/AB

You will probably land on this page looking for an answer to a question we ourselves had some months ago.

You want to choose a solid foundation for your next project, which requires a CMS, and you have very compelling reasons to do it in Ruby on Rails, but you don't know the existing options all too well.

Luckily for you, we have been testing the most popular CMS solutions in the market that have been built with Ruby on Rails for you.

Five reasons why our clients love Ruby on Rails for their apps

Captain's log, stardate d33.y37/AB

As a specialised development consultancy, we work on projects of all sorts. In our first two years of existence, we learnt a lot about client-side work. You can find our recap on our blog entry We Don't Need a CEO (Lessons Learnt in Two Years Running a Development Consultancy).

Our tech stack is based on the framework Ruby on Rails and Ruby as the programming language, for which we sometimes receive some objections, saying it's not solid or popular enough. Our clients think otherwise, and we have summed up the five main reasons why they love Ruby on Rails for their projects.

Four things we do to reduce the time to market of your app

Captain's log, stardate d19.y37/AB

In over two years and a half of existence, we have had the pleasure of working on more than thirty different projects from different sectors (fintech, social entrepreneurship, marketing, e-commerce, 3D printing, etc.) for our clients in different countries (USA, France, Germany, Spain, Finland, etc.).

From all these projects, we have learnt many lessons. One of them is that we are able to reduce the time to market for your project so you can maximise your chances of success. Read further!

You're one step away from meeting your best partner in business.

Hire Us