Mobile app development has become a must for companies and businesses. Users (and customers) are found on mobile devices. But the huge variety of environments poses a real challenge for managing resources. Various platforms, several operating systems, different needs. There are solutions available today that enable the unification of application development and design efforts.
When developers are considering creating a mobile app, the first thing they should ask themselves is for which platform. Is it an app for iOS, for Android, for Windows Phone or for other operating systems like Blackberry, Tizen or Firefox OS? For iOS we need a programmer in Objective-C or Swift that uses the integrated Xcode development environment; for Android, the programming is done in Java and Eclipse can be used as an IDE; and for Windows Phone, development is done in C# or HTML5 in Visual Studio (Microsoft).
Faced with such a diversity of operating systems, there are two alternatives for not having to use different languages and IDEs for each application:
– Use a development framework such as Xamarin to program in C# language the code that will be shared by all the applications and develop the user interface for iOS, Android and Windows Phone separately. At Xamarin they believe that C# is the best syntax for developing mobile apps, better than Objective-C, Swift or Java.
– Resort to tools like Apache Cordova or PhoneGap, that enable applications to be developed in HTML, CSS and JavaScript.
What Apache Cordova provides
Apache Cordova is an open source development framework for programming multiplatform mobile apps in the three standard web project creation languages: HTML5, CSS3 and JavaScript. It is therefore not necessary to use native solutions or languages for each platform. How? It uses standard APIs to access the components and functions of each device.
1. Apache Cordova use cases:
– Make a single application that can be uploaded in all possible app stores: for example, App Store or Google Play.
– If a programmer wants to code an interface using native components for each device and WebView, Android provides a built-in browser for their apps.
2. Development components in Apache Cordova:
– All applications designed in Apache Cordova are based on a global configuration file, config.xml. This XML file conforms to the standard specifications of W3C's Web Application Packaging (widgets), irrespective of the type of platform. For projects created using the Cordova CLI (command line interface), this XML file can be found in the path app/config.xml.
– The applications in Apache Cordova are implemented as a web page, within a local testing host in the file index.html. And the app is run on a WebView within the native structure of the application itself. This browser provides the app with all the features and functionality offered by the user interface.
– Proprietary or third-party plugins can be added with Apache Cordova to enhance the application's functionality. There is a third-party plugin registry on this list and, if an own development is preferred instead, it must always be programmed according to the specifications of this Cordova Plugin Development Guide.
3. How to get started:
– Install Apache Cordova: The Cordova command line runs in Node.js, so first we need to install this multiplatform execution environment on the server side. It is possible to add all kinds of dependencies needed for developing the application, here is a specific tutorial for doing so. The Apache Cordova installation command: npm install -g cordova.
– Create a new project using the command line: In the directory, choose where the project should start and run the cordova create <path> command.
– Launch the application for the platform already installed in Apache Cordova: Run the cordova run <platform name> command.
What PhoneGap provides
The first thing we have to say is that technically speaking, PhoneGap and Apache Cordova are the same tool. There are no major differences between them: They are open source solutions for developing multiplatform applications in HTML, CSS and JavaScript, without the need for using different languages and development frameworks for each OS.
The company that created PhoneGap, Nitobi, transferred the tool's source code to Apache Foundation in 2011, which gave rise to the Apache Cordova project in 2012. With Nitobi's acquisition by Adobe in October 2011, this solution kept the name PhoneGap, in open source but with the possibility of enriching it with added functionality. They are therefore two identical tools with two different names.
Is there any interesting difference between them? Yes. Adobe enables the integration of PhoneGap with its compilation services (Adobe PhoneGap Build), which saves you having to download and install the SDKs for each environment, as happens with Apache Cordova. This is not necessary because the compilation is done by the tool. This is an advantage.
PhoneGap enables the development of applications with standard APIs that provide access to all the functionality offered by most devices. This table shows how this tool works with the different terminals.
1. How to get started with PhoneGap
– Install PhoneGap: You can implement it on your desktop for both Mac OS X and Windows. The app's interface is created using a simple 'drag and drop' function, without installing the PhoneGap CLI.
– Install PhoneGap Developer App: This application installed on the mobile device helps programmers run tests with the product they are developing. It automatically provides access to the basic APIs of PhoneGap to work with the native functions of each device without installing SDKs, plugins or compiling anything locally. It enables easy development testing.
– Create the application: A new project is opened (it usually creates a Hello World project by default) and the local path where the future application will be hosted is chosen. It is also possible to create applications with PhoneGap using a combination of native components both for products in iOS and Android and using WebView.
Open finance is expected to be regulated over the next few years, leading to a new open data ecosystem Open finance is making its way into the legal system through the consolidation of several initiatives that will lend it legal protection. Once this is complete, customers will have an open finance framework that protects their data […]
APIs are the future of automated banking services. Albert Pla, Head of SME eSales in BBVA Global Markets, tells us about this technology. APIs are one of the newest and most highly anticipated tools in Open Banking. They can automate business processes and allow bank transactions to be carried out without leaving the company’s work […]
Real-time payments have become one of the most noteworthy innovations in the financial industry. Their growth in recent years has been significant thanks to the possibilities they offer companies, especially in customer relations.
Please, if you can't find it, check your spam folder
×
The email message with your ebook is on the way
We have sent you two messages. One with the requested ebook and one to confirm your email address and start receiving the newsletter and/or other commercial communications from BBVA API_Market
×
PROCESSING OF PERSONAL DATA
Who is the Data Controller of your personal data?
Banco Bilbao Vizcaya Argentaria, S.A. (“BBVA“) with registered address at Plaza de San Nicolás 4, 48005, Bilbao, España and Tax ID number A-48265169 . Email address: contact.bbvaapimarket@bbva.com
What for and why does BBVA use your personal data for?
For those activities among the following for which you give your consent by checking the corresponding box:
to receive newsletter from BBVA API_Market through electronic means;
to send you commercial communications, events and surveys relating to BBVA API_Market to the e-mail address you have provided.
For how long we will keep your data?
We will keep your data until you unsubscribe from receiving our newsletter or, if applicable, the commercial communications, events and surveys to which you have subscribed. Whether you unsubscribe or whether BBVA decides to end the service, your details will be deleted.
How can I unsubscribe to stop receiving newsletters and/or communications from BBVA API_Market?
You can unsubscribe at any time and without need to indicate any justification, by sending an email to the following address: contact.bbvaapimarket@bbva.com
To whom will we communicate your data?
We will not transfer your personal data to third parties, unless it is mandatory by a law or if you have previously agreed to do so.
What are your rights when you provide us with your information?
You will be able to consult your personal data included in BBVA files (access right)
You can modify your personal data when they are inaccurate (correction right)
You may request that your personal data not be processed (opposition right)
You may request your personal data be deleted (suppression right)
You can request a limitation on the processing of your data in the allowed cases (right of limitation of processing)
You will be able to receive, in electronic format, the personal data you have provided to us, as well as to transmit them to another entity (portability right)
You are responsible for the accuracy of the personal data you provide to BBVA and to keep them duly updated. If you believe that we have not processed your personal data in accordance with regulations, you can contact the Data Protection Officer of BBVA at the following address dpogrupobbva@bbva.com.
You can find more information in the “Personal Data Protection Policy” document on this website.
×
PROCESSING OF PERSONAL DATA
Who is the Data Controller of your personal data? Banco Bilbao Vizcaya Argentaria, S.A (“BBVA“), with registered address at Plaza de San Nicolás 4, 48005, Bilbao, España, and Tax ID No. A-48265169. Email address:contact.bbvaapimarket@bbva.com
What for and why does BBVA use your personal data for?
For the execution and management of your request, specifically, download the requested e-book/s.
BBVA informs you that, unless you indicate your opposition by sending an email to the following address: contact.bbvaapimarket@bbva.com, BBVA may send you commercial communications, surveys and events related to products and/or services of BBVA API Market through electronic means.
For how long we will keep your data?
We will keep your data as long as necessary for the management of your request, and to receive commercial communications, events and surveys. BBVA will keep your data until you unsubscribe to stop receiving our newsletters or, where appropriate, until the end of the service. Afterwards, we will destroy your data.
How can I unsubscribe to stop receiving newsletters and/or communications from BBVA API Market?
You can unsubscribe at any time and without need to indicate any justification, by sending an email to the following address: contact.bbvaapimarket@bbva.com
To whom will we communicate your data?
We will not transfer your personal data to third parties, unless it is mandatory by a law or if you have previously agreed to do so.
What are your rights when you provide us with your information?
You will be able to consult your personal data included in BBVA files (access right)
You can modify your personal data when they are inaccurate (correction right)
You may request that your personal data not be processed (opposition right)
You may request your personal data be deleted (suppression right)
You can request a limitation on the processing of your data in the allowed cases (right of limitation of processing)
You will be able to receive, in electronic format, the personal data you have provided to us, as well as to transmit them to another entity (portability right)
You can exercise before BBVA the aforementioned rights through the following address: contact.bbvaapimarket@bbva.com
You are responsible for the accuracy of the personal data you provide to BBVA and to keep them duly updated.
If you believe that we have not processed your personal data in accordance with the regulations, you can contact the Data Protection Officer at the following address: dpogrupobbva@bbva.com
You can find more information in the “Personal Data Protection Policy” document on this website.
Banco Bilbao Vizcaya Argentaria, S.A. owner of this portal uses cookies and/or similar technologies of its own and third parties for the purposes of personalization, analytics, behavioral advertising or advertising related to your preferences based on a profile prepared from your browsing habits (e.g. pages visited). If you wish to obtain more detailed information, consult our Cookies Policy.
Cookie settings panel
These are the advanced settings for first-party and third-party cookies. Here you can change the parameters that will affect your browsing experience on this website.
Technical Cookies (required)
These cookies are used to give you secure access to areas with personal information and to identify you when you log in.
Name
Owner
Duration
Description
gobp.lang
BBVA
1 month
Language preference
aceptarCookies
BBVA
1 year
Configuration Accepted Cookies
_abck
BBVA
1 year
Helps protect against malicious website attacks
bm_sz
BBVA
4 hours
Helps protect against malicious website attacks
ADRUM_BTs
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BT1
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BTa
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BT
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
xt_0d95e
Salesforce Marketing Cloud
Session
Remember user preferences (if any)
__s9744cdb192d044faa1bf201d29fafd1e
Salesforce Marketing Cloud
Session
Remember user preferences (if any)
wpml_browser_redirect_test
WPML
Session
Text translation in the portal
wp-wpml_current_language
WPML
24 hours
Text translation in the portal
They are used to track the activity or number of visits anonymously. Thanks to them we can constantly improve your browsing experience
Your browsing experience is constantly improving.
With your selection, we cannot offer you a continuously improved browsing experience.
Name
Owner
Duration
Description
AMCV_***
Adobe Analytics
Session
Unique Visitor IDs used in Cloud Marketing solutions
AMCVS_***
Adobe Analytics
2 years
Unique Visitor IDs used in Cloud Marketing solutions
demdex (safari)
Adobe Analytics
180 days
Create and store unique and persistent identifiers
sessionID
Adobe Analytics
Session
Launch's internal cookie used to identify the user
gpv_URL
Adobe Analytics
Session
Adobe Analytics plugin: getPreviousValue Capture the value of a certain variable in the following page view, in this case the prop1
gpv_level1
Adobe Analytics
Session
Cookie used to store the DataLayer levl1 of the previous page.
gpv_pageIntent
Adobe Analytics
Session
Cookie used to store the pageIntent of the previous page.
gpv_pageName
Adobe Analytics
Session
Cookie used to store the pagename of the previous page.
aocs
Adobe Analytics
Session
Cookie that stores the first values collected at the beginning of a process.
TTC
Adobe Analytics
Session
Cookie used to store the time between the App Page Visit event and the App Completed event.
TTCL
Adobe Analytics
Session
Cookie used to store the time between the LogIn event and App Completed.
s_cc
Adobe Analytics
Session
Determine if cookies are active
s_hc
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_ht
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_nr
Adobe Analytics
2 years
Determine the number of user visits
s_ppv
Adobe Analytics
Permanent
Adobe Analytics plugin: getPercentPageViewed Determine what percentage of the page a user views
s_sq
Adobe Analytics
Session
ClickMap/ActivityMap features
s_tp
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_visit
Adobe Analytics
2 years
Cookie used by Adobe to know when a session has been started.
They allow the advertising shown to you to be customized and relevant to you. Thanks to these cookies, you will not see ads that you are not interested in.
The advertising is customized to you and your preferences.
Your choice means you will not see customized ads, only generic ones.
Name
Owner
Duration
Description
OT2
VersaTag
90 days
VersaTag Cookie used to store a user id and the number of user visits.
u2
VersaTag
90 days
VersaTag Cookie where the user ID is stored
TargetingInfo 2
MediaMind
1 year
Cookie that serves to assign a unique random number that generates MediaMind.
These cookies are related to general features such as the browser you use.
Your experience and content have been customized.
With your selection, we cannot offer you a continuously improved browsing experience.
Name
Owner
Duration
Description
mbox
Adobe Target
9 days
Cookie used by Adobe Target to test user experience customization.
×
Looks like you’re browsing from Mexico, so let’s show you the custom content for your
location. Change
Looks like you’re browsing from Spain, so let’s show you the custom content for your
location. Change
Select a country
In order to access the private area and corresponding sandbox, select the country of the APIs you want to use.