MOBILE APP DEVELOPMENT
FOR BUSINESS.
From idea → to pop app
We develop convenient mobile apps
EN
RU
OUR CASES
02
ROSTELECOM
03
RUSSIAN AGRICULTURAL BANK
04
05
06
SMART HOME
SAZAWEAR
MEDCARD24
01
PETSEE
07
PETS
08
Rental Property
PRODUCT VISION.
First, we dive into your market, make a list of primary tasks and the concept of a mobile application with API and T3.
APPLICATION DEVELOPMENT
We develop mobile apps with design, UX / CMJ, which integrates with your block end system.
APP + BACK-END
If necessary, we attract a separate team of java developers and create a full-fledged project.
BUILDING A HIGHLOAD ARCHITECTURE
We create a separate infrastructure for high loads so that the app withstands tens of millions of users.
DIGITAL 360°
If your business grows fast, we will add additional communication channels (weareables, smart TV, etc.). We use the
DevOPS set and sign the SLA.
ABOUT OUR TEAM
Our team is a single body that works without failures, provided that we lead a correct lifestyle.
As often happens in business, in 2019 our team took up the issue of creating a mobile application for their own needs.

During the development of the application, it was foreseen to face a series of questions:
- how to choose a contractor for work;
- how not to overpay for a project too much;
- what is the difference between platforms and which one to choose: native or cross-platform application, etc.

After a while, we began to understand that we understand much more about creating mobile applications than 50% of companies in this area.

After 1 year, we firmly decided to open our own direction in our company for the development of mobile applications. We created a team and received the first projects from our clients.

The Hunterprice Digital team today is a synergy of experience, honest and understandable pricing for a project + competencies tested on our own experience.

OUR BLOG
Let's figure out what to choose: Development of a native or cross-platform application. We answer briefly and to the point.
Reading time: 5 minutes.

Text: As a rule, the access of any business to the Internet proceeds according to the following scenario: first, the company launches a website, then it is adapted for mobile devices, and if there is an increase in traffic, it makes sense to gain a foothold among the owners of mobile gadgets, and the company releases an application.

There is no point in comparing a mobile site and an application - the latter definitely wins due to the breadth of its capabilities and a responsive interface, which is much more comfortable to interact with via a phone or tablet. In addition, the application can work without a permanent internet connection.

Whether your business is built on sales, service delivery, or outreach, it's impossible to ignore the time people spend in front of mobile screens today.

This article aims to cover two approaches to application development - native and cross-platform.

Each of the approaches has its own specifics that critically affect the final result. And in order to facilitate understanding between the customer and the developer, I would like to talk about what both approaches are, to disassemble their advantages and disadvantages, to destroy the entrenched stereotypes about development and to answer the main question: how to make a choice in favor of this or that approach according to the principle of expediency.

1️⃣ Native approach
Native apps are apps that you experience from day one of using the device. These are the default browser, email client, address book, alarm clock, calendar and other standard programs.

How do I create a native app? If developers in the process of writing an application use a programming language adopted for a specific platform, be it Objective-C and Swift for iOS or Java for Android, such an application will be called native (from English native - native, natural). Native people can get access to all the services, services and gadgets of the phone: camera, microphone, geolocator, accelerometer, calendar, media files, notifications and so on - in general, they fully settle down and feel at home.

2️⃣ Cross-platform approach
What are cross-platform applications? Imagine a mobile site that does not always need the Internet, and in terms of design, it is closer to mobile applications rather than web pages. This is roughly how you can describe cross-platform applications. So what to write cross-platform applications on? They are often written in a markup and styling language (HTML, CSS and JavaScript) just like mobile sites. The logical justification for doing this is that, after all, all Internet content is HTML pages. Such applications are written simultaneously for all platforms and are adapted to most devices, because the browser engine is mainly used for their work.

3️⃣ Hybrid applications
As you can see, the bar for entering the more than promising area of mobile application development has dropped significantly. Someone might think that now layout designers who do not go beyond the proven HTML and CSS will take bread from real programmers. Others see the cross-platform approach as a future in which the time and cost of developing applications will be fully optimized. There are arguments on both sides explaining why this rather than another approach to development is correct.

But when we are talking about solving certain problems, it will be more effective to combine these approaches - to use the cross-platform advantages of HTML to design content, and make the menus and controls that are demanding on responsiveness native, spending a minimum of effort, time and budget. These applications are called hybrid applications. In this case, only the amount of native code determines which approach is more appropriate for application development.

What situations lead to convergence of approaches? Let's say a client wants a simple news feed with nothing but text and images. Based on this task, the developer decides to use a cross-platform approach. But if after a while the customer wants the application to store a large amount of data or to process sound and graphics, the task becomes more complicated. For these purposes, you need to write native code for each specific platform, and a once completely cross-platform application turns into a hybrid one.

It is a common misconception that behind any icon on the user's desktop, a native application is waiting. This misconception is so deeply rooted that even in professional circles, they sin with formulations of a high degree of absurdity, such as "native phonap application". But you can even display a shortcut for the site on the desktop, so the icon does not guarantee anything, and both a native application and any other can be on the other side with equal probability.

Comparison of approaches

The supply market is growing. Mobile application sales statistics show that from year to year, gadget users are increasingly changing standard services to alternative ones. So, the native task manager is replaced with Wunderlist, the mail client - with the Mailbox application, Evernote turns out to be preferable to standard notes.

It is important for the customer to know the advantages and disadvantages of each of the approaches and not to overestimate expectations when making a choice. Comparative analysis will be appropriate for a number of criteria.

Platform Dependency

One might get the impression that a cross-platform application is comfortable on all platforms, even the most unpopular ones. A caveat is required: for this belief to be true, you may have to write a piece of additional code for each platform. In the case of native applications, you can count on their excellent work, but for each platform you need to develop its own version.

Interface design

It is impossible not to touch upon the guidelines in the context of mobile app development. Guidelines are valuable guidance from platform companies to mobile app developers to align their design and functionality to standards. Guidelines are the foundation on which the psychology and comfort of platform users is based. Simply put, interface elements have a familiar look and feel.

The language environment in which native mobile applications are developed has the necessary tools to create an interface familiar to the user. The situation with web technologies is different: it takes a lot of effort to make a cross-platform application look like a native one. Various cross-platform frameworks (Framework 7, Sencha Touch, Kendo UI, Ionic and others) help to simulate the native interface with varying degrees of reliability, but most often the responsiveness, animation speed, effects and design will be different. The next paragraph is devoted to this.

User experience

The first thing a user subconsciously expects from his application is responsiveness. The user's action is immediately followed by a response, page scrolling and animation proceed smoothly and without freezing. Cross-platform applications in this regard are significantly inferior to native ones, and if you do not beat around the bush, they slow down, and this is their main problem.

Also, the user is sure that each control, each icon will have a standard appearance and position on the application screen. For different platforms, these standards will be different, and if the creation of a cross-platform application was carried out according to the iOS guidelines, then Android users will be uncomfortable, and vice versa.

One of the brightest examples is the Back button: this is a typical Android feature that has no equivalent on iOS. Therefore, when you create a cross-platform mobile application, there can be only two compromises in this situation: either the design is the same for both platforms, and users of one of them are forced to adapt, or you create two different designs, taking into account the characteristics of each platform. In fact, in the second case, two applications are created, but in the same cross-platform language.

Limitations

A native application written for a specific platform feels like its full-fledged inhabitant, getting maximum access to all devices and services of the device. When designing a cross-platform application, the developer takes into account only the capabilities of the framework that imposes its own limitations.

It can also create a problem that the frameworks have many versions, and the older the version, the more restrictions. In any case, not all platform features are open to a cross-platform application. The need for full integration does not always arise - its depth depends on the tasks that the application must solve.

Safety

For all popular browsers, there is a standard secure data transfer protocol - HTTPS. But if a special level of encryption is required, the solution to this problem lies with the developer. Ensuring reliable data protection is possible only with native development of mobile applications, since it is associated with mathematics, and such operations require the most efficient use of hardware resources.

Service and support

Comprehensive maintenance of native Android and iOS applications (finding and fixing bugs, updating and any minor changes), on average, takes twice as much resources due to the need for at least two different specialists (iOS and Android). A cross-platform application can be managed by one developer.

The cost of mobile development and the time spent is entangled in misconceptions and myths, and therefore I would like to touch upon these issues separately and if not dot the i's, then at least contribute to this.

Fast and cheap cross-platform app development - myth or reality

Cross-platform mobile app development is cheaper, which is explained by the smaller amount of work relative to native development. But there are also pitfalls here, which can be discerned only by understanding the principles of pricing.

It should always be remembered that time and cost are governed by the complexity and quality of the task. Let's say that for the development of a cross-platform product, we have one specialist who knows HTML, CSS, JavaScript and has experience in PhoneGap. One specialist is one abstract resource unit (let's say, one person-month).

To work on a native application, two such resources are required - iOS and Android. As a result, it takes two man-months to complete a native project, and 1.5 to complete a cross-platform one.

The question will be fair: "How so - one and a half? Why not one? " Alas, in practice, a cross-platform application that works well on iOS will not work well on Android - all browser engines have their own specifics, and as a result, optimization for Android may take another half man-month.

Based on the foregoing, the cost of mobile development was calculated in the case of the native and cross-platform approaches, presented in two tables. The results in Table 1 are based on the average hourly rate of freelancers from the freelansim.ru and fl.ru databases in rubles, in Table 2 - the average hourly rate of freelancers and studios from the international database upwork.com in dollars.

When we compared the approaches according to several criteria, we said that the degree of integration of the application into the platform is due to the complexity of the problem being solved by the application. Using a template or a ready-made solution can be a fairly cheap way to make an application, as long as the capabilities of the template or solution are sufficient for the specific task.

But there is a nuance

And it lies in the structural feature of the application. Most often, it involves the presence of a server part, where application users save data and through which they exchange them with other users, and it also requires financial investments. Work on it can take up to a third of the entire development time, and it increases when you need to create an administrative panel for easy data management.

Let's summarize
- you should resort to native development if;
- your application requires free access to all resources and services of the phone;
- you want to get the most responsive application;
- the application must be able to work offline;
- your application should make the most of the device hardware.

Cross-platform mobile development is your option if:
- you are willing to put up with low responsiveness;
- the application does not involve complex animation and does not deal with calculations; - the application needs constant internet access to download content;
- you need to go to market quickly to test an idea; you have a website and you want to wrap it up in an app for a minimal price.

Individual circumstances always lead to the choice of a particular strategy; no article will give a universal answer.

Our material rather provides background information of a general nature, to help the customer and the developer to establish a dialogue in a language that is understandable for both.

The final decision should be made after consulting the developers. The more arguments you hear about a particular approach, the better.

Outcome:

We tried to summarize the final results of our analysis in such a table, indicating the most basic parameters for comparing the two development options.

We remind you that our Hunterprice team provides services for the development of mobile applications and web services. We offer you the development of both cross-platform applications and native ones, and we are always ready to help you make the right choice.
Development of mobile and web applications: which is the best solution.
Reading time: 5 minutes.

Text: Recently, our clients have been faced with the question of what should I develop for my project: a mobile application or a web version, or maybe both?

There are a lot of such questions, so this article was born. In it, we approached the issue as constructively as possible and analyzed it from all sides. We invite our reader to study all our collected experience and already make a decision on what will be needed for a particular project. So let's go!

The topic of choosing between mobile and web applications was, is and will be relevant. Both options are popular, each of which has both advantages and disadvantages.

In general, everything is not difficult: in order to accurately determine the choice between the development of mobile and web applications, you need to consider several criteria.

First of all, these are the goals that you want to achieve (and the functions that the application should have), the target audience and your budget. Before moving on to looking directly at mobile and web applications, let's first define a web application.

A web application is a client-server application (the client is a browser, and a web server acts as a server), in which data is stored mainly on the server, and data is exchanged over the network.

From this it follows that to work with a web application, the user needs access to the Internet.

A distinctive feature of a web application is its scale: a large number of people can use it at the same time.

One of the advantages of choosing to develop a client-server application is the fact that users are not dependent on the operating system, so web applications are cross-platform.

The disadvantage of a client / server solution is its dependence on the network. If a user installs a mobile application on the phone directly from the application store (Google Play, App Store), he can use it offline, then with a web application this will not work, he always needs the Internet.

Also, with an expensive Internet connection, you can "fly in a pretty penny". In terms of payment for the end user, a monthly fee is usually required to operate a web application (usually a small amount).

Also one of the options is to make payments based on the transactions performed.

If the user is late with the payment, then access to work with the web application is closed. Thus, the client is, as it were, attached to the provider: he cannot refuse his services (or not pay) and at the same time continue to use the application.

Sometimes the web application is provided for free, but the user is offered premium features that must be paid to access.

One of the undoubted advantages of web applications is that they do not require installation on a smartphone. That is, they do not take up memory on the device (only a little cache), unlike mobile applications.

Nevertheless, it should be noted that in terms of functionality, the development of a mobile application gives more than client-server development, but it also requires more costs and time.

In this regard, a web application is a good choice, especially if you need something fairly simple and does not require a wide range of complex functionality, for example, a news feed.

We should not forget the fact that the mobile application almost always goes in addition to the web, i.e. the company starts with developing its web application, and only then moves on to developing a mobile one.

Another advantage of developing client-server applications is that you can always update them, at any time, and this does not cause any difficulties: after that, the new version of the application will be available to all users.

The situation is different with mobile applications: when updating (for example, design), making any improvements and developing additional functions, a new version is obtained, which the user again needs to download from the store.

Nevertheless, the promotion of a web application often requires more expenses than for a mobile application, although client-server development itself is almost always cheaper (for similar functionality).

The whole point here is that app stores themselves are good advertising, in which a user who wants to install an application looks at various options and compares reviews, product ratings, and also sees the number of downloads.

Of course, there is also a minus in the sense that if the application, let's say, is not very good, then the reviews will also be appropriate.

Marketing is one of the most important stages: before developing a mobile application, you should analyze your competitors, the market, and the needs of your target audience.

The idea should be relevant, and the product should meet all user requests, be convenient to use, etc.

Then you get good reviews, downloads, and ratings: the mobile app stores themselves will be the best ad for you. And in the end you will be successful.

At the same time, when promoting a web application, significant costs for search engine optimization (SEO) are often required, and often the funds saved on development go to marketing.

The key point is the audience: people almost always go to app stores specifically to download an application with the necessary functions, and then the question of choice is: what they like, where the reviews are better, the rating is higher, etc.

And for the success of a web application, it is often necessary to invest heavily in its promotion (with mobile too, but not to such an extent, there is more a question of the correct approach to application development).

Another advantage of developing mobile applications is that you can be sure that you are not downloading any virus for yourself. App stores check everything carefully before making an app available for download.

Mobile apps also have access to device storage (and more), unlike web apps, which ask for certain privileges during installation.

Another great advantage of developing a mobile application is that you can get into the user's head and firmly settle there. What we mean: mobile apps keep you connected with your customers.

You, not them, make contact and maintain it. You can send useful newsletters, notify you of discounts and promotions, congratulate you on the holidays, and more - everything to increase your sales and at the same time provide your users with excellent services.

Now let's summarize and list the advantages and disadvantages of developing mobile and web applications.

➕🖥️ Benefits of web applications:
- Web apps don't require installation on your phone, unlike mobile apps, so they don't take up space on your smartphone. All you need to work is a browser and the Internet - you don't need to install any special software to use the web application.
- Development of client-server applications is usually cheaper than mobile applications. - When updates are made to the web application, they are carried out on the site automatically.
- The costs of developing web applications itself are lower.

➖🖥️ Disadvantages of web applications:
- There are not so many opportunities in the development of client-server applications as in the development of mobile.
- Payment - mostly charged monthly (subscriber) or based on the volume of transactions. - The web application may be provided free of charge, but you must pay for premium services or features.
- Possibility of "getting a virus" or that your data will be misused. You cannot work offline, only if you have the Internet. And don't forget about traffic.

Now let's move on to mobile applications.

➕📱 Benefits of mobile applications:
- Great opportunities in the development of functionality, and as a result, the result is better and more user-friendly (with similar functionality).
- You can work offline - there is no dependence on the network (except for some cases when, for example, to use some of the application's features, you need the Internet). - Target users are already entering the mobile app stores, so there is no need to spend too much money on SEO promotion, as in client-server development.
- Mobile apps are much better optimized for mobile devices.
- All content is already inside the mobile application, i.e. you do not need to reload all the data every time, as when working with a web application. Less cost of product promotion. - Be in touch with your customers - users of the application.
- You can constantly send them information about discounts, special offers - do everything to keep them interested in your services.

➖ 📱 Disadvantages of mobile applications:
- The process of developing mobile applications is longer and more costly than client-server development (with similar functionality).
- A mobile application almost always comes as a necessary addition to the web (goals can be different: to increase sales, optimize business processes, increase employee productivity, always "be in touch" with your customers, etc.).
- If there are any difficulties in use, or any shortcomings in the product, users may leave not the best reviews in the app store.

Outcome:

As you can see, developing both mobile and web applications has its advantages and disadvantages, and sometimes the choice is not so easy.

Be mindful of your audience, opportunities, and project goals. We hope we have provided you with detailed and helpful information to help you determine the best option for your future project.

If a mobile application is the optimal solution for your project (for example, you already have a web application), then next you will need to make a choice between developing a cross-platform and a native application.

Our article on the advantages and disadvantages of native development and cross-platform application development will help you with this "We figure out what to choose: Development of a native or cross-platform application. The answer is short and to the point."

Our Hunterprice team provides mobile app and web services development services. We offer you the development of both cross-platform applications and native ones, and we are always ready to help you make the right choice.

We also provide web application development services. The use of the best technologies and practices in work, as well as a team of experienced developers allow us to create the highest quality products.

CONTACTS
8 (800) 511-40-60
Hunter Price LLC
OGRN 1157456021480
620075, Yekaterinburg, Malysheva st., 51
office 24 / 03 (BC "Vysotsky")
Enter data
Fill in the brief
Choose project scope
Your budget
Describe the task
CASE 01
OJSC Russian Railways is a Russian state vertically integrated company, the owner of the infrastructure of most of the
rolling stock and the main operator of the Russian railway network.

BACKGROUND
: To be clear right away, not only our team participated in the development of the mobile application. This is a huge project with several teams working on it. We completed only part of the task.
CASE 02
Russian Agricultural Bank Rosselkhozbank is a Russian state bank. It is one of the 30 largest banks in Russia, occupying 5th
place in terms of assets and 4th place in terms of equity (Q2 2019).

BACKGROUND: The bank is considered to be not a high-tech bank.

OBJECTIVE: To create an app that will increase customer's convenience and loyalty to the bank.

COMPLICATIONS: The problem lies in the fact that the customer has already started developing the app and the project
has been "frozen".

SOLUTION: It is difficult to continue someone else's work - it is easier to start all over again. So we did))

RESULT: we've got a classic and functional application for the bank.

CONCLUSION: if you took on someone else's project - close it and start afresh. This is proved by mistakes and many
years of experience!

CASE 03
Rostelecom is a Russian telecommunications company. The largest national digital services provider. It provides high-
speed Internet access, interactive television, cellular communications, local and long-distance telephone communications, etc.

BACKGROUND
: Our team did not create a turnkey application for PJSC Rostelecom. We worked on a project and did only one of many points while developing the application.
CASE 04
Smart home is a modern approach to manage your apartment.

BACKGROUND
: a company engaged in the construction of residential buildings contacted us. They build so-called "smart
homes". Such an object requires specific software.

OBJECTIVE
: To create a functional and modern app for managing a "smart home".

DECISION
: We decided that the app should contain the following elements: Home screen, divideв control for rooms and
devices, a schedule setting, statistics.

RESULT
: We've got a simple and functional app for your "smart home".
CASE 05
SAZAWEAR - a large and modern online store of cloth for women.

BACKGROUND
: The company faced the task of introducing a new channel aka a mobile app.

OBJECTIVE
: To attract new customers and keep regular ones by developing a mobile app for the online store.

SOLUTION
: An introductory onboard of 3 screens is created in the mobile app that appears at startup and introduces the
user to the app. A catalog has also been created with the search and a list of the main categories. Convenient product cards
with price and product names have been added.

RESULT
: Our customer got a modern, fast and convenient app for online sales.
CASE 06
MEDCARD24 is a mobile app for scheduling online appointments with a doctor.

BACKGROUND
: Our customer wanted to implement his idea, namely, to create an app for online scheduling and
receiving medical care.

OBJECTIVE
: To draw the design of the future app, to coordinate it with the customer. To create and coordinate a
prototype of a future app. To implement it all in one app.

SOLUTION
: It was decided to include: a patient's personal account, a patient's medical history, treatment plan, online
doctor search, measurement diary, organizer.

RESULT
: A convenient and modern option for patient interaction with the attending physician.

CASE 08
Pets is a mobile application for finding pets.

BACKGROUND: Launch a pet search and sale startup.

TASK: On the basis of the terms of reference, prepare a prototype of the future application. Develop and launch an MVP model.

SOLUTION: Our team has developed a modern design, taking into account all the wishes of the client. The project was completed 30 days ahead of the agreed deadline.

RESULT: Modern service for finding and buying pets.
CASE 07
Petsee is a mobile GPS pet collar app.

INITIAL DATA: Roman turned to us to develop a mobile application for his new project.

OBJECTIVE: To develop a convenient application with a modern design to implement the function of a GPS transmitter for tracking pets.

SOLUTION: It was decided to make the application in a cross-platform version to reduce costs.

RESULT: Convenient and modern way of interaction between the patient and the attending physician.
CASE 09
Real estate rental is a mobile application for searching and renting real estate.

INITIAL DATA: It was required to run the MVP model of the application to test the hypothesis of our client's business.

OBJECTIVE: Launch the application with minimum costs and maximum functionality.

SOLUTION: The application was developed on a cross-platform version.

RESULT: Simple classic design and attractive project cost.