Developing an app can be an expensive and lengthy process, which means integrating useful tools that cut down costs can increase the potential for your app to be a success.
Building an app from scratch is a time-consuming endeavor. You need to create the most efficient and cost-saving process to increase your app’s chance of success. What tools and practices can you use to cut down app development costs?
In this article, we’ll discuss 5 different tools that professional app developers use to build better apps faster:
- Free and commercial APIs and web services, such as the Google Speech API
- Production-ready iconography and graphics templates, both free and paid
- Firebase and similar Backend-as-a-Service (BaaS) providers
- Tools like Apptentive, to get user feedback and speed up product iterations
- And the “holy grail” of app platforms: cross-platform development tools…
Not Invented Here: APIs And Webservices
Some developers suffer from the so-called “Not Invented Here Syndrome.” Developers sometimes prefer to build a tool themselves, instead of relying on third-party frameworks, libraries, and tools.
Building an app entirely in-house and from scratch, however, takes much more time and effort compared to using ready-made solutions, even when those tools need customizing.
Take Google Cloud’s web services for example. The Cloud Speech-to-Text (STT) web service can transform spoken audio in real-time, transcribed text. At about $0.024 a minute, it costs a fraction of what it would take to develop accurate speech recognition from scratch.
Your developers need to get up to speed with a new API. An API or application programming interface is a set of definitions, protocols, and tools for creating software. A new API outweighs the cost of operating and maintaining a cloud service yourself.
Another benefit is progress: Google continually improves its web services, by using insights gathered from widespread use of its APIs. It is nearly impossible to reach that scale of knowledge on your own.
The same principles apply to many more APIs and web services. When you’re planning to build an app, and it could potentially make use of an API, it’s worth it to do a simple search for “[tool] API” or “[solution] web service.”
Don’t Create Your Own Icons
Icons are notoriously hard to design from scratch and, every few years, the mobile app development platforms change their icon and graphic styles.
Between iOS 6 and iOS 7, icon styles transformed from bold, complex, color-rich icons to duo-tone, flat, and thin-lined icons. Imagine you designed an icon set just before iOS 7 came out. All your icons would look hopelessly outdated! So, why design from scratch if you can pick up an attribution-free icon library for less than $100 – or for free?
Glyphish is one such icon pack. It has 2200+ icons in different styles and sizes and typically releases new icons for every next version of iOS. Icons can be directly imported into Xcode.
Another icon set is Font Awesome. What’s different about Font Awesome is that it’s a vector-based font, instead of separate PNG/SVG icon files. Fonts are easier to compress and use less bandwidth and storage. You can directly use the fonts in Xcode or Android Studio.
What if you need a custom icon? Icons8 has a solution. Icons8 is a searchable library of free icons, so you can find the exact style you’re looking for. If you need a custom icon, Icons8 can then provide it to you for a small fee. It’s easier than designing a complete icon set by yourself.
Building A Back-end With Firebase
Imagine you’re building a social media app. How do you let users see each other’s posts? Most developers would use a cloud-based back-end to store user data.
Building a back-end usually involves three components:
- Integrating the back-end with the client apps: i.e. the code that moves data from and to the back-end.
- Bringing the back-end online: i.e. by hosting and running it on a web server.
Every one of these components needs to be built, configured, and maintained. Building a back-end from scratch takes a lot of time, and scaling web servers to provide your web service internationally is a complex and costly operation.
What if you could short-circuit this process?
Instead of building everything yourself, you build your back-end on top of existing infrastructure, such as Firebase or Parse Platform. The only thing you need to do is set up your database and integrate it into your app.
Firebase offers a cloud-based back-end, called Firestore, to save user data in the cloud. It’s available for many platforms, including iOS, Android, and the web. Firebase runs on Google’s worldwide infrastructure, and it provides other services, such as push notifications and ad monetization.
Parse Platform, an alternative to Firebase, runs on your own infrastructure. It’s an open source platform, and that means you can modify and expand the platform yourself, and freely install it on any web service like Heroku, Amazon Web Services, Docker, or Azure. Thanks to many open source contributions, app developers can adopt a suite of tools with the click of a button.
Collecting User Feedback Early With Apptentive
If you’re developing an app with an agile or lean approach, user feedback is particularly important to the evolution of your app. User feedback is key to your app’s survival, in fact.
According to Apptentive, 73.2% of people are likely to leave a review after a negative app experience. This means that if you’re using app reviews as the only input for app improvements, you’re likely to collect lots of bad reviews, and you’re slow to improve your app based on feedback.
Apptentive has developed a suite of tools that allow you to proactively engage with your app’s users, and collect their feedback as early as possible.
This engagement is of paramount importance for app publishers building their minimum viable product (MVP) and especially interesting for teams that use agile development, such as Scrum.
You can directly pipe user requests and bug reports into your agile workflow. As a result, the development cycle of app improvements shortens, and you can respond faster to feature requests.
Is Cross-Platform Development Worth It?
The idea of cross-platform development is simple: it is a tool that exports your app to both iOS and Android with one codebase. Learn app development once, and build for any platform.
iOS and Android aren’t compatible, because they have different programming languages, SDKs, and APIs. You need to develop one app twice if you want to reach both iOS and Android users. A tool that can slash your development time in half appeals to most developers.
Flutter is a newcomer in the industry. Instead of building on top of native, like React Native, it completely sidesteps the native iOS and Android SDKs. An app built with Flutter has a separate runtime that handles the drawing of UI and user interaction. This runtime works on both iOS and Android.
The big question is: are there any cross-platform tools that allow you to build apps for both iOS and Android with the same codebase? Technically, yes.
It’s recommended that you consider a cross-platform tool in light of the tool’s strengths and weaknesses, as opposed to simply not wanting to build the same app twice. Building an app with the wrong cross-platform tool is, ironically, the best way to double your development time.
How Will You Speed Up Development?
We’ve looked at several tools and technologies that can speed up your app development. Within icons and back-ends and APIs, a common theme emerges. It’s often not worth it to build an app entirely in-house and completely from scratch. If you are still unsure how to streamline your development process, hire an experienced mobile app development company.
The question only you can answer is: what are you going to build internally, and what can you outsource to external tools and technologies?
About the Author
Reinder de Vries is a professional iOS developer. He teaches app developers how to build their own apps at LearnAppMaking.com. Since 2009 he has developed a few dozen apps for iOS, worked for global brands and lead development at several startups. When he’s not coding, he enjoys strong espresso and traveling.