TemaBit interviewed by GoodFirms


TemaBit interviewed by GoodFirms

Kindly share your feedback on how GoodFirms has been doing so far in increasing your visibility among potential clients.

Goodfirms has been a tremendous help in providing visibility. I wish I could use the platform to reach out to potential customers….webinars based on the Goodfirm platform or something like that to generate sales traffic.

Please introduce your company and give a brief about your role within the company?

TemaBit is a solution provider that solves everyday enterprise challenges such as scalability, redundancy, down timing. We provide business intelligence analytics, packaged software products as well as SW development, database development, mobile application development, UX/UI Design, QA Services. We work with body-shopping, team-shopping, project-based outsourcing approaches. We are fluent in most of the technologies.

What was the idea behind starting this organization?

The idea was to utilize our experience and create solutions that help businesses to operate. TemaBit has had extensive experience in mobile solutions, web solutions, we also have had deep dive in such specific fields as BPMS, assortment, price management.

Temabit can provide a solution expertise and can develop/customize/ a solution for your needs, as well as provide you development resources.

What are your company’s business model–in house team or third party vendors/ outsourcing?

We work with body-shopping, team-shopping, project-based outsourcing.

How is your business model beneficial from a value addition perspective to the clients compared to other companies’ models?

We have obtained experience in solution design across all spectrum of business processes as well as we developed expertise in most of the technologies. We can provide you not only development services but technological and business consulting.

What industries do you generally cater to? Are your customers repetitive? If yes, what ratio of clients has been repetitive to you?

TemaBit is a solution provider that works across all spectrum of business processes. The most familiar for us is retail and cross retail solutions such as vendor, warehouse, data management. We are extraordinarily strong in mobile, payment, point of sale solutions.

We have more than 70% of our customer base who is our repetitive customer base.

Mention the objectives or the parameters critical in determining the time frame of developing a mobile app.

In an ideal world, to determine the time frame we need to have a statement of the problem in the form of technical specifications or at least BRD, a list of recommended technologies, a list of limitations, a functional architecture diagram, a list of systems, and protocols for integration. Ideally, you need an app design as well.

How much effort in terms of time goes into developing the front end and back end of a mobile app?

It depends on complexity but on average, it may take between three and six months to develop an app. A typical team for a mobile application consists of three developers – back, iOS, Android. They work synchronously and are 100% occupied. In terms of resources, the front end is twice the times longer than back. 3-6 months is an average period for a mobile application of medium complexity.

What are the key parameters to be considered before selecting the right platform for a mobile application?

You must know the answers to these questions:
What is your budget for app development? Does it reconcile with the cost?
What is your target user? What is the behaviour of that user? From here you should know the features you want to incorporate, a device it needs to support. The technology you want/require to use.

Which platform do you suggest your clients to begin with when they approach you with an idea (Android or iOS) and why?

In most cases, a customer gets to us with a clear vision of what to choose.
IOS or Android. Both offer an extensive range of features. Android, however, is slightly different on devices from different manufacturers, IOS is uniform.

If the customer does not know which platform to choose, our recommendations are based on a business idea, depending on the target audience of the product. In general, we do not have a preferred platform; they are equal for development.

Android or iOS, Native or Hybrid — which platform is best to use to build your app? What are your recommendations?

Hybrid or Native:
Hybrid is developed using HTML, JavaScript, and CSS. You can run it anywhere, performance suffers compering to Native, but it is cheaper and faster to develop. Native Apps are developed using platform-specific language, separate code for each platform. It has higher cost and development time, but no need to spend time after for customization, also native apps add privilege of functions that are specific to OS on which those apps are built. Speed to market, one source code, easy updates, availability of resource makes Native more attractive. But later, a company will spend more time for customization.  Native apps give advantages of functions that are specific to the operating system.  Building on Native makes more sense for long term strategy.
It is important to add here these:  Ionic (Apache Cordova), Xamarin, React Native, Flutter, Android Native (Java / Kotlin), iOS Native (Obj-C / Swift).
1. Ionic is a hybrid, I described it already (HTML / CSS / JS, it slows down, but it is quick to develop). The disadvantages include non-native display and behaviour of controls.
2. Xamarin, RN, Flutter – these are toolkits that are compiled into native code. Pros – up to 90% of cross-platform code, that is, development acceleration compared to a pure native, cons – can be a little slower than native, UX may differ from native, technologies are still developing, and are not completely stable. RN is Facebook, Xamarin is Microsoft, Flutter is Google.
3. Java / Kotlin, Obj-C / Swift – I mentioned it already.
Ionic can be offered for rapid prototyping, or for maximum cross-platform, for example, for corporate products, when only employees will use it, and a unified interface is required.
Java / Kotlin, Obj-C / Swift – for public products where UX should be as native as possible
Xamarin, RN, Flutter – where you need close to native performance, but you need to reduce the development cost.

What are the key factors that you consider before deciding the cost of a mobile application?

Complexity of the solution, hours we put in.

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.)

It depends on our agreement but generally, it is post-payment after the task is delivered.

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?

Our budget requirement starts from $8k per project. The initial project can be less if we agree on a technological forecast with a customer.

What is the price range (min and max) of the projects that you catered to in 2019?

Our average rates 29/h across all technologies.

Which business model do you suggest to your clients enabling them to generate revenue from mobile applications? Why?

It highly depends on industry. For example, if it a loyalty system we suggest enable in-app purchase, in -app marketing, rating system, maximum involve your customer in usage of the application. To be able to monetize your app you will need to consider all key strategies, such as: In-app purchases, in app advertising, subscription, data usage. You will have to pay attention to cost-per-impressions, cost-per-click, cost per sale networks, cost per install networks, cost per view. To use or not Freemium upsell.

Vitalii Panchenko

CEO, TemaBit

Find us at GoodFirms