Any entrepreneur knows the difficulties involved in validating your idea and turning it into a reality. While it may be hard, taking risks is crucial to gain traction and buzz about your design or new product. How do new business owners know whether or not their concept is feasible, or if it’s going to benefit consumers? The solution is an MVP or minimum viable product.Read More
As anyone experienced with Rails production applications might know, there are times when certain features or parts of an application cause high memory usage and/or unacceptably slow response times.
In that past, there have been some pain points around deployments for Elixir and Phoenix 1.4, and after managing some production deployments we realized that the available tools, such as Distillery and Edeliver, have greatly reduced the complexity of deployments.
We’re continuing our series on building a simple Software-As-A-Service (SaaS) application using React, Redux and Firebase. We’re utilizing Firebase as a Backend-As-A-Service (Baa), and building a simple application that demonstrates some of the core features.
We’ve been exporing different Backend-As-A-Service (BaaS) options and decided to publish a short series on how to build a simple Software-As-A-Service (SaaS) Application using React, Redux and Firebase.
While testing a feature that requires a confirmation, you may have seen a:
There are two different ways to accept the confirm alert in an acceptance/feature spec:
In the last post we wired up some of the UI with remote requests to our local api from our SPA section using React. In this post we’re going to continue fleshing out our CRUD features and wrap up the series.