View Case Study
The blueprint that has been developed leaves me with confidence to expand with new features, that will respect many of the lessons learned during wireframing and prototyping with Ildikó.Tim Koopman
View case study
We are delighted with the result, which has transposed into increased online sales and positive feedback from our customers. We look forward to continuing to work with reinteractive on future developments and enhancements to ensure that we stay ahead of the game.Zlata Relin
If you are not completely happy with the result when we are done, we will give you $10,000 worth of our development time, at no charge, to make it right.
reInteractive's Rails Installfest initiative helping hundreds of developers get introduced to Ruby on Rails. We welcome people brand new to Rails get their first Rails blog online in one night!
Development Hub is our monthly free gathering where you can work on whatever Ruby on Rails problem you like. Get help to debug that annoying bit of code or just come and hack, all are welcome!
We have reached the point where if your business doesn’t exist on mobile you are suffering serious disadvantages regardless of what you are selling or providing. Deciding between what to build is a topic that needs its own blog post. Discussing the native app, hybrid app vs mobile website/responsive website topic is a separate one that I wouldn’t like to get into today. For the purposes of this post I will assume that you have decided on the right solution for you and that happens to be a native app. What can you do to ensure its success?
Context is crucial to the success of any app. With the web it’s easy - people will be using it while sitting at a desk or at least sitting with a laptop somewhere. With mobile, it can be any number of places and situations. If you’re building an app for runners, think of what features they can and should access while running. For example, for a runner it’s very useful to know their heart rate, their speed, track their movements on a map, see how many calories they’ve burned and have the ability to share their progress with their peer group. All of this is great to have in a mobile app, but should you have it all present at once? Or does it make sense to have a big “Start/Stop” button that takes up the whole screen? If you go with the start/stop button, how large should it be? What’s the ideal size to prevent accidental taps while in motion, but at the same time prevent the runner from having to stop to activate it? Or, what about a GPS app for mountain climbers? They probably don't have available hands to fiddle with their device while trying to keep safe. What features are still useful, and how can you ensure that your app is actually usable in the real world?
When engaging a software developer to develop a bespoke system, it is tempting to imagine that hiring inexperienced software developers is a smart move that saves money. Experience shows that this is not always the case.
Imagine you have a ten storey building to build, but due to budget constraints you want pay for each storey as it is completed and only build subsequent floors after the previous floor is built and occupied. You are taking a MVP approach to skyscraper building!
Last week, I fixed an interesting issue and want to share it with you.
It first came from a bug report when a user found that one of the PDF's logos was missing. Because we use wickedpdf to generate PDFs, naturally, the first thing I did was open the html we serve to wickedpdf in the browser. And guess what, the logo was showing correctly in my browser. That is strange, so I open the html template and check the source code, and what I found was something like this:
These days it seems that everyone is out there developing an app to handle some problem they believe everyone has. People seem to think that if they can just get their app built, then their biggest problem will simply be beating away users who will be demanding access to it and who will be throwing money at them...
As the founder of a web application development agency, you’d think I would be bouncing up and down like a kid in a candy store with this state of affairs, and to be truthful, there is a lot of demand for our services, but we turn away more work than we take on.
Many companies have business processes that are a manual time-sink. These processes generate unwanted excess traffic and extra work in trying to get the job done. Not only do they take precious minutes (or hours!) out of your team's day, but they also result in mistakes, missed details and slipped deadlines.
But identifying which of these processes would benefit the most from automation can seem like a dark art. In a perfect world, everything would be automated and we would live in the paperless office nirvana sipping our favourite beverage and clicking "approved" or "denied" as new items came to our attention.