Loading...
Answers
MenuWhat are reasonable price levels and time scales for an intuitive, usable mobile app?
What is easy and what is hard in mobile app development? What do you have to pay for quality? The app I have in mind already has a web version with developers who can write API hooks. For intracorporate use, ten thousand simultaneous users max.
Answers
Great question - my firm builds and helps migrate/support dozens of mobile apps each year. There are several questions that need to be answered before a reliable estimate can be given. For example, are you strictly seeking a native mobile app? If so, which platforms? Will the mobile apps shared a backend with the existing web application, or will it be stand alone? have you outlined the UI and UX yet? produced wirefarmes, technical specifications documents or any information architecture outlines?
Simply put, there are items in most mobile app projects that do tend to require more time investment (which next to the location of where you build the app is of course the most important driver of cost/quality): this would include things like UI/UX, API documentation, Technical Documentation and Testing- most of the time, the actual core development of an application (assuming you are investing in the above appropriately) comes down to block and tackling and just executing the strategy you lay out ahead of time.
All of that being said, based on the limited information I have now, this certainly sounds like an application that could be on the faster side of the delivery timeline. If you'd like to get a few drilled-down and accurate tiers on pricing, timeline and some suggested next steps, feel free to reach out and we can discuss further over a quick call.
The key is to understand how apps are built and maintained and what is the relative cost, benefit, and downfall of each option. Before we get into the biggest hidden costs of app development, it is important that you understand the mobile app architecture. Let us drill deeper into each of these to see which individual roles they play in your mobile app costs. It is hard to imagine an app that does not utilize this essential mobile capability. If you want push services, you will need a service like UrbanAirship or PushWoosh. You will want to use these services to encourage sharing and upvoting your content through social media. To integrate SMS messaging into your mobile app, you will have to use a service like Twilio. As a creative professional, you want to be in control and avoid calling the IT department every time you want to access your data or update content. The traditional app development solution does not offer a way to save up on these costs. Simply not including these in your app management is not an option as it would take away your control over the content, users and data. If you can edit a Word document, you should be able to edit your app content – this capability is a must for your dashboard. Dashboard emulator. You will want to see how changes you make look on the app before pushing them outlive to the user community. Functional services management. Separate dashboards for each of your services are very impractical. Capabilities like monitoring social behaviour and sending push notifications, emails and SMS are vital for your app, and routine tasks of managing these services should all be available from a single dashboard. Dynamic updates. Some apps require an elaborate resubmission process every time a simple content change is made. Ensure you build in a dynamic update process whereby a simple click of a button on the app dashboard pushes out the content changes to all apps automatically. User profiles. You will need a way to manage your users’ profiles. It is unlikely all administrators or users will be the same. Data segmentation. You will want to classify users into different categories based upon activity, profile, and other parameters. This is useful for messaging and push notifications to users based on a segment they fall into.
These services include infrastructural components such as where the app is hosted, where data is stored and how the data is delivered. Data storage. Data is king, and your app will collect and contain a lot of it. It is crucial that you understand how and where the data will be stored. CDN services are provided by companies like Akamai, CloudFront and Dyn. Images data. Most apps use a lot of images. Such services are provided by companies like CloudImage.io, Google and ImageX. Development tools, libraries, and support. If you are using paid deployment tools like IBM MobileFirst, Kinvey, Kony or Appcelerator to develop your apps on, you will need to subscribe to it over the life of your app. While these services are not an actual part of the app architecture, ongoing technical support is the critical component of any app deployment and it may account for large costs over time. Your resources should always enable you to address the following iOS and Android updates. Even if you have a dynamic update process, there will be times when updates require resubmission. Every app usually has multiple third-party APIs they interact with, especially at the enterprise level. Changes to any of these applications will require periodic maintenance of your APIs. User communities are not kind to apps that are slow to address the issues they report. Maintenance costs. The key issue with mobile app development cost is the number of individual components you need to assemble. You have seen in our mobile app development cost breakdown that these costs grow into the most expensive items in your mobile app budget, continuing for as long as your app is available. You only pay us a fixed monthly subscription, which gives you access to all the features and abilities to develop, deploy, and maintain your mobile app from a single dashboard. It simply means you will never have to pay the high costs of infrastructure and code maintenance, analytics, or expensive developer hours for a simple code fix.
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
Any opinions on raising money on Indiegogo for an app?
Apps are difficult to fund on IndieGoGo as few are successful, and we rarely take them on as clients. Websites like http://appsfunder.com/ are made for that very reason, but again, difficult to build enough of a following willing to pay top dollar for an app that could very well be free, already existing in the marketplace. A site that is gaining more traction you may want to look into would be http://appsplit.com/. Again, Appsplit Is Crowdfunding For Apps specifically.RM
-
If I am planning to launch a mobile app, do I need to register as a company before the launch?
I developed and published mobile apps as an individual for several years, and only formed a corporation later as things grew and it made sense. As far as Apple's App Store and Google Play are concerned, you can register as an individual developer without having a corporation. I'd be happy to help further over a call if you have any additional questions. Best of luck with your mobile app!AM
-
What is the best technology for developing a new mobile app from scratch?
There are two sides to that question. One is the mobile app itself and the other is the backend. If I misunderstood in any way and you didn't mean "native" app I apologize in advance. On the backend, there is no clear cut answer to which is the "best". It depends solely on the developers you are able to get. We for example use Node.js , mongoDB, redis, elasticsearch and a couple of proprietary tools in the backend. But you have your pick of the litter now both on the backend api and the datastore with the myriad of options available and touted as the "best" currently on the market. Now on the app side again it solely depends on what you need your mobile app to do. Experiencing first-hand "develop once, run anywhere" I can say it's more like "develop once, debug everywhere" to quote a Java saying. We have tried Phonegap and Titanium Appcelerator and we have switched to native (ObjC and Java) after a couple of months of trying to go the hybrid route. The reasons behind the choice are as follows: - anything that breaks the pattern of how those frameworks NEED to operate is just a huge technical debt that keeps accruing a huge interest. - anything that uses css3 accelerated animations on Android is buggy at best and slow as hell at worst on any lower (< 4.1 I think) versions of Android I hope this gives you some insight. If you need/want to ask me anything feel free to contact me. MihaiMP
-
Whats are some ways to beta test an iOS app?
Apple will allow a developer to register 100 UDID devices per 12 month cycle to test via TestFlight or HockeyApp. Having started with TestFlight, I would really encourage you NOT to use it, and go directly to HockeyApp. HockeyApp is a much better product. There is also enterprise distribution which allows you far more UDID's but whether you qualify for enterprise distribution is difficult to say. As part of your testing, I'd encourage to explicitly ask your testers to only register one device. One of the things we experienced was some testers registering 3 devices but only used one, essentially wasting those UDID's where we could have given to other testers. Who you invite to be a tester should be selective as well. I think you should have no more than 10 non-user users. These people should be people who have either built successful mobile apps or who are just such huge consumers of similar mobile apps to what you're building, that they can give you great product feedback even though they aren't your user. Specifically, they can help point out non obvious UI problems and better ways to implement particular features. The rest of your users should be highly qualified as actually wanting what you're building. If they can't articulate why they should be the first to use what you're building, they are likely the wrong tester. The more you can do to make them "beg" to be a tester, the higher the sign that the feedback you're getting from them can be considered "high-signal." In a limited beta test, you're really looking to understand the biggest UX pain-points. For example, are people not registering and providing you the additional permissions you are requiring? Are they not completing an action that could trigger virality? How far are they getting in their first user session? How much time are they spending per user session? Obviously, you'll be doing your fair share of bug squashing, but the core of it is around improving the core flows to minimize friction as much as possible. Lastly, keep in mind that even with highly motivated users, their attention spans and patience for early builds is limited, so make sure that each of your builds really make significant improvements. Happy to talk through any of this and more about mobile app testing.TW
-
Where can I find programmers willing to join a growing mobile start up for equity only?
You won't find anyone worth adding to your team willing to work for equity only, no matter how compelling your product and business is. The realities of the talent market for mobile developers anywhere is such that a developer would be foolish to work only for equity unless they are a cofounder and have double digit equity. Happy to talk about hiring and alternatives to full-time hires.TW
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.