The population keeps business cards (from the plumber, the electrician, the bakery), and when you need the services of these professionals … where’s the card? Busca is an application designed to solve situations like this. It is an app that we developed for iOS and Android that connects the customer with service providers. Through Buscaki, you can find professionals in twenty categories (and more than two hundred types of services provided) near you. Busca makes it possible for you not only to discover the professional but also to talk to him by message or chat . Just in time. Busca was built using geolocation tools. That is, when the client searches for a professional, the first names that appear to him are the closest to his home. The user can register more than one address in Buscaki. For example, the user may have his / her residence in the city registered, as well as the house on the beach, or the place inside. And seek the professionals closest to the address where you will need the services.
The idea came to the app’s creator, the entrepreneur Felipe Reis, from his disgust at seeing his mailbox full of pamphlets and business cards every day. An informal survey started with acquaintances: who kept these advertising materials for professionals? The answer: none. “The professional make a folder or business card, spends fifty, one hundred reais, but his return is very low”, says Felipe Reis. With the idea germinating, it took shape, definitely, when Reis consulted a general service provider if he would advertise in an app like the idealized one. “On the spot” was the professional’s response. Thus was born Buscaki, which already has 240 registered professionals. For now, it is available in Curitiba and the metropolitan area.
Understand the benefits of the native app over the hybrid
Everyone knows that people love their smartphones. And the main reason for this affection is the apps that run on them. For this reason, we at DevMaker invest in quality in the development of mobile applications. Between native or hybrid development, we chose to develop apps only natively. You will understand why. (Oh, and we’ve already explained what “native” and “hybrid” mean).
Well, to start, let’s give a brief explanation about the two types of apps.
Native applications are programs developed for a specific platform (for example, an application specially built to run on the iPhone, with the iOS operating system; or else an app developed to run on a smartphone with the Android operating system; or on the Windows Phone). In other words, a native application is designed to run perfectly on that specific operating system, extracting its full potential. The hybrid application is developed in a mixed way, a little bit in the language of one operating system, a little bit in the language of another. In general, beneath its application shell, the hybrid app pulls content from the web (for example, from the website of the company that owns the application). Developing a hybrid app can be more economical. But the quality of the native is still superior. There are ardent defenders of both, with good arguments from side to side. However, on the native side, there is an unbeatable argument for your choice. The best argument that can be found in any market.
It’s the user experience.
It is a fact: people love smartphones, as we said. They develop a personal relationship with them. (Do you know someone who lost his cell phone and shrugged: “No problem, tomorrow I buy another one”?). This affection does not arise from the device itself, but from what is inside it. In other words – it doesn’t hurt to repeat – because of the applications. That is, the application has to give the user great user experience. As there are many of them on the market, a bad experience makes the consumer quickly abandon the app that does not work well. For example, only 16% of users, according to research, try to install more than once the app that “bugged” the installation.
The experience of using the native app is unquestionably superior. The hybrid application is faster and cheaper to develop. But always remember the user who is going to use the application. He expects the app to be bug-free and quick to use (often, the hybrid app, because it has to load web content, unlike the native app, whose data pack is already complete when downloaded, is slower to use ). That is, the user’s expectation is that the app has a wonderful performance. And here lies the problem with the hybrid app. The style and internal logic of the iPhone and Android are very different from each other. When building a native app for each one, these differences are taken into account. As skilled as the developer of the hybrid application is, he, trying to bridge the gap between the two styles, will not be able to get close to the user experience of the native app.
A second technical argument: you have developed a hybrid app that depends on loading data from the web. This means that the user will not be able to use the application when offline (when there is no wi-fi nearby or the 3G or 4G signal is bad or non-existent). Not to mention the common conflicts that hybrid apps have with smartphone hardware, such as the camera and GPS. This all frustrates the user. It is a demanding market, and everything that is below the goodwill, sooner or later, end up in the cell phone’s trash. The reaction of 92% of customers who have a negative experience with the application is generally one of two options: 1) never use it again; 2) download the competitor’s application.