Please introduce your company and give a brief about your role within the company?
TRooTech Business Solutions helps connect deeply the brands to enrich the digital experience of the end-customers and make a remunerative business. We shape the business ideas by offering custom-tailored business services by being a top-rated full-stack developer using native technology that caters to and compliments the exact requirements of start-ups and enterprises with a resourceful team and process for developing top-notch web application, mobile application, custom software, apps for IoT, wearables, Bluetooth devices, and form integrated solution using different databases and server technologies.
My chief role is to communicate cash flow management aspects to the board, firm’s vision to prospects, clients, employees and business partners, team roles to the individuals and brand value to the market. Apart from that I also develop and lead the executive team here.
What was the idea behind starting this organization?
Downrightly, I would say that Priyank and I witnessed the then development scenario which largely consisted of project abandonment and hugely extended time issues.
We even saw that the clients were losing their trust from the small and large development industries and the freelancers were gaining the development market place by making more and putting the clients under risk of irresponsible work. When we witnessed this dissatisfaction around us, we learnt the first and foremost business lesson - the driving force behind any innovative business idea is to work in entirety. More or less, here we direly felt the need to reduce the friction that existed between the clients and the developing firms. We wanted to bring back that missing element of trust in this business.
And you see, with the same urge to retain the trust and produce potential digital products that sustain in markets for making or helping business of clients, TRooTech was conceived and is growing up commemorating the same business principles.
What is your company’s business model–in house team or third party vendors/ outsourcing?
We have an in-house team for the development and research purposes who work under fixed price, time, material, and dedicated resource hiring as engagement models.
Our in-house team consists of tech and functional analysts, UI/UX and front end designers, software developers, app developers for Android and iOS, QA professionals, team leads and project managers who manage resources on firm’s end while managing communication with the clients.
It is really important for the clients to be familiar with the technical aspects for a long run in the industry. I personally make sure to collaborate with the clients as much as possible in order to educate the clients technically and bring them on the same development page as that of the project gurus.
How is your business model beneficial from a value addition perspective to the clients compared to other companies' models?
We have in-house resources which is one benefit as whatever we are doing on the project we are directly responsible for it and the turnaround time reduces there. Apart from the industrial terminologies, we believe our approach is helping us a lot into our business model, that is, we go deep in understanding the requirements before we confirm the project. This helps the prospects gain more trust in our work. This also helps us to deliver the project with near-perfect evaluations and thus we are able to achieve project completion within the pre-determined timeframe. Once the perfect execution of the application occurs along with giving the additional details to the prospects in their own plan, our attention to those details, we don't have to sell anymore, it just happens.
In near future, we are coming up with another model we define as Similar App Development. Often start-ups entail into getting everything done and making the best product looking at the competitors or references, that enthusiasm is good but not everybody sees behind the lens of the reference app, those are hidden pages for aspiring start-ups. We have got a technical view and can very nearly judge from the timeline and progress of any reference apps, that from time to time what has worked for them and what has not. So we have introduced this model wherein prospects specifically can request for similar app development pointing at one app or a similar one and on their behalf, we do detailed study of it, tailor the plans according to what suits our prospects based on multiple factors and then produce a perfect solution. It's receiving quite a buzz and was selected for vendor briefing in Gartner last year.
What industries do you generally cater to? Are your customers repetitive? If yes, what ratio of clients has been repetitive to you?
Majorly we work encircling the industries - Omni-channel ecommerce and Marketplaces, Social Media, Social Networking, Social Bookmarking and Social Games, Travel and Hospitality, FinTech, EdTech, Logistics and Transportation, Event Management, Entertainment Portals, by covering all their niches and segregations.
When we undertake a project, we proceed with an aim to work and complete the project and brief about the same to our clients. This business sense helps our client develop trust in us.
Yes, most of our customers are repetitive and we have maintained a retention rate above 95%.
Mention the objectives or the parameters critical in determining the time frame of developing a mobile app.
I would say, before estimating the time frame, we analyze the uniqueness of the idea - whether it needs experimentation or is similar to the already existing applications. And here the client's collaboration plays an important role. So a considerable amount of time goes in educating them about the various technical and development aspects. Here a lot of time can be saved if the clients are responsive and willing to learn and yes, with a seamless process, the project becomes a cakewalk.
Next, the technical complexity of the project is taken into consideration. Here the main aspects such as the features, unique selling point, whether to develop the minimum viable product or is it to be launched with an advanced set of functions, integration of the third party software, customized software, or does it require an independent set of functions is considered and the time is estimated accordingly.
Moreover, when the application is a consumer-facing application, the parameters of its interaction are taken into consideration. Accordingly, prototypes, wireframes, and mock-ups are tested with the end-users and the difficulties they face during interaction are examined and are altered.
Another important feature can be whether the development is only for the core application or the entire app system. You know many a times, the project requirements are such that it only demands core app development on front end features and their implications. In such cases, the clients have the design ready and our work is to develop and fit in the requested operations. Other than this, there is app system in which the client comes up with the idea and the entire development is undertaken from the scratch needing designing, front end, back end, database management, web services/APIs and third party integrations
How much effort in terms of time goes into developing the front end and back end of a mobile app?
Now, these are the factors that vary from application to application and so no generalized time can be quoted for this. I would say it is based on the app idea. But if even the minute details are clear and all the development scenarios are analyzed well with the required information about the APIs is with us then I can quote a general time duration for the frontend development which is about 70-90 business days and the backend takes about 120-150 business days.
What are the key parameters to be considered before selecting the right platform for a mobile application?
The basic parameter that matters is - the product itself.
Yes, gone are the days when clients didn't know what to look for. Today, they have turned smarter and they try to grasp the technical concept of the application along with the market evaluation. Thus, most of the times, it is the clients that come up with the platform preference.
But when the decision is trusted upon us, we heavily research on the demographics, the target audience, interests, and habits of device usage for that specific business domain and try to understand which platform makes best sense.
Which platform do you suggest your clients to begin with when they approach you with an idea (Android or iOS) and why?
Whether iOS or Android for us is directly proportional to the functionality of the app. For instance, when we say there is an involvement of the end-user, the platform with an Android or iOS is more feasible and easy to use. On the other hand, when there is an involvement of the admin with the task to manage the operations, a web application is more feasible.
Other than this, all I can say is, we don't bifurcate between only Android and iOS since every single day there are new OS coming up with the latest technologies. So, apart from the conventional choices between the Android, iOS, and web application, we make sure to develop a platform that best shapes the idea.
Android or iOS, Native or Hybrid — which platform is best to use to build your app? What are your recommendations?
Talking about the OS, it certainly depends on the need of the clients. What we aim at is providing quality to the application and so it's native or nothing for us. Definitely, native applications out-perform the hybrid applications. Many of our competitors provide the development using hybrid applications however we strictly don’t.
These new frameworks that help in the development of hybrid applications undoubtedly reduces the development time and are cheaper. But behind the curtains of so much easiness, there comes certain level of infeasibilities and instability of products developed through it. And I have a point to make here. See the instability issues are way high for the application with the development of such frameworks. In many cases, the application misbehaves with the core functions of devices and does not support some features. More we experimented with the hybrid technology, the more we found flaws and instability issues with it. Thus if we already can develop quality applications using native technology, we don't feel the need to go for the hybrid methods.
And why only quality, native based applications are sustainable and are ready for the future expansion of the features.
What are the key factors that you consider before deciding the cost of a mobile application?
About the key factors I would say that a run-through analysis is very crucial in deciding the cost of the project which is why we communicate with the clients and make sure that we are on the same page as the clients in the matter of the features and the interpretation of the project. Secondly, it involves the development for the backend and the aspects that complete the application.
The estimation is dependent on the revenue model of the business as well. For example the development of the features for the commission is way different than the development of advertisement revenue model. Other than these, the cost can be decided as per the project and the resources we provide - UI/UX designers, backend developers, frontend developers, analysts, team size for the project, and whether the app idea is consumer facing or for the enterprise.
Next, on the basis of how the project backend is and what type of third party integration is needed. Also, the cost relies on what kind of dynamic behaviour is needed for the backend and what features, more or less, are to be involved, allowing the managing of features in it rather than being system managed.
The statistics/reports as part of analytics of development consumes a lot of time and is a crucial parameter for the overall cost estimation.
What kind of payment structure do you follow to bill your clients? Is it Pay per Feature, Fixed Cost, Pay per Milestone (could be in phases, months, versions etc.)
This question could be better answered if we diligently focus on the engagement model that we offer.
For the fixed price engagement model we usually follow Pay per milestone payment structure wherein we conscientiously define the milestones that are to be delivered along with the timeline.
When the project is based on the Time and Material or Dedicated Resource as Engagement Model, we charge the project on monthly retainer basis or longer contracts.
Do you take in projects which meet your basic budget requirement? If yes, what is the minimum requirement? If no, on what minimum budget you have worked for?
Yes, we usually take up the projects that are above US$10K as native apps, below $10K of budget produces compromise somewhere.
What is the price range (min and max) of the projects that you catered to in 2016?
The minimum price was around US$13K and the maximum for the year 2016 was around US$65K.
Which business model do you suggest to your clients enabling them to generate revenue from mobile applications? Why?
We can suggest revenue models only for consumer facing apps and that too if they are start-ups. Revenue model also depends on the nature of business and business domain of the app.