2 ms·
You may have needed 30-60 days to build an App in the past because development eats up so much of that time. You should still start with a real problem, do goo
by blueprint 15y ago
You may have needed 30-60 days to build an App in the past because development eats up so much of that time.
You should still start with a real problem, do good planning and market research, as well as validation of your solution, and that can take time, but no longer will you need weeks and weeks to implement the App. The company I run, Blueprint (https://blueprint.io https://blueprint.io), is basically a tool like Illustrator for people who want to build iPhone apps. Best of all, unlike a bespoke App which has to have its code opened up and then be republished each time a change is necessary, Apps you build with Blueprint can be updated with almost any kind of change while they are still in the wild.
Now, 30 days doesn't consist of 1 - 2 weeks for planning and design and 2-3 weeks of fast coding and testing - it can consist of 3 weeks of design and a few days of building your App for free. You can even use Blueprint to preview your App live in your browser and gather feedback from your target audience before you commit to paying the one-time fee for sharing releases. It's a new way to approach the process of creating mobile Apps.