0% found this document useful (0 votes)
90 views2 pages

Plagiarism Scan Report: Plagiarised Unique

The document discusses various approaches to mobile application development. It covers native development, where an app is developed for a single platform using that platform's tools and languages, which can be time-consuming but provides the best performance and user experience. Hybrid development is also discussed, where an app is developed once then deployed across platforms, but may have issues with limited resources, wireless connectivity, or device variety. The document analyzes the pros and cons of different mobile development approaches.

Uploaded by

Khushi Kashyap
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
90 views2 pages

Plagiarism Scan Report: Plagiarised Unique

The document discusses various approaches to mobile application development. It covers native development, where an app is developed for a single platform using that platform's tools and languages, which can be time-consuming but provides the best performance and user experience. Hybrid development is also discussed, where an app is developed once then deployed across platforms, but may have issues with limited resources, wireless connectivity, or device variety. The document analyzes the pros and cons of different mobile development approaches.

Uploaded by

Khushi Kashyap
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

PLAGIARISM SCAN REPORT

Date 2020-12-31

Words 993

0% 100% Characters 6392


Plagiarised Unique

Content Checked For Plagiarism

Mobile app development is a special case in the development of software, because developer needs to consider various aspects including
the short development period, the capability of mobile devices, mobility, the requirements for mobile devices, the screen sizes, the design
and navigation of the App user interface, security and user privacy, etc., and marketing needs for the apps. The lifecycle of the mobile app
production includes: (1) App concept review, (2) configuration of the UI, (3) development of the framework using the target platform tools
and programming languages; (4) on various devices checking the software, and then finally (5) the publication in the target platform store of
the application. The successive versions of such app in the target application store release new features or changes to the App. The above
development cycle is replicated for each target Platform in order to build the mobile app for several platforms except for the first step in the
review of the App's specifications. To build the same app on each platform, the development tools of every platform and the correct
configuration, at least one smartphone device, a tablet device for each platform and often multiple devices for the same platform, such as
Android, are required to create one App for all platforms. In order to publish the created applications, it is important to build a developer
account for each platform store. PROBLEMS WITH GENERATING MOBILE APPLICATIONS If apps are built with a mobile or multi-platform
approach, during the development process programmers and designers face similar challenges. The most common problems include : the
limited resources of mobile devices, wireless communications and the variety of mobile devices. • Limited resources - Mobile devices are
getting more powerful year after year, and display resolution is growing. The device's battery is considerably limited in size to maintain low
weight and dimensions, particularly thickness. Therefore, it is important to maximize the energy usage in the process of developing a mobile
app. Upgrades which cause considerable battery drain reject users. The application logic should mainly cover planning operation, the way
the application interacts with the server or the minimal CPU-intensive activities. The application logic should be designed. • Wireless
communication- The smartphone's most significant feature is the ability to use several wireless connections. In addition to GSM phone calls
and communication via Bluetooth with other devices, the Internet is also accessible through HSDPA and LTE mobile networks or through
traditional wireless Internet networking networks. Each route is just one problem, depending on the requirements. The existence of
interferences, communication errors and wide bandwidth gaps characterize wireless data transmission. A major challenge is thus to ensure
that applications run smoothly irrespective of the connection type and quality. Wireless networks are vulnerable to attacks, and so you
should be especially careful to encrypt and authenticate applications running on sensitive data. • The variety of mobile devices- On the
market there are a wide range of mobile devices. A number of sizes, aspect ratios and screen resolutions are provided by Android and iOS.
From 4-inch cell phones on the low end to large tablets in which the resolution reaches up to 4K through high-end models of 5-inch high-
pixel screens. Mobile apps should operate correctly irrespective of the device form. There is no standardization of internal system
components. By developing a mobile app with a specific built-in sensor, a situation where no such sensor is on the computer must be
treated (or it is damaged). APPROACHES OF MOBILE DEVELOPMENT Mobile development model is the most successful one which can
meet all needs, boost development times and manufacturing costs for the desired app. It may often be difficult to build the mobile app. The
list of requirements should include simplicity and the ability to incorporate changes which meet business requirements and market
requirements promptly.Mobile development approaches include items such as native, mobile web, hybrid and cross compiled. Native The
phase of mobile apps on a range of platforms is a time-consuming job. Each of the three major platforms uses another language of
programming. The primary language for the Apple devices running iOS is Objective-C. The default programming language of Android
devices is Java. Windows Phone is using C#, the primary language is C#. It can take a lot of time for developers to learn a new language for
a particular platform. The option to add new developers to other platforms already fluidly may be expensive for an enterprise. If a decision
has been taken to add a new interface to the current application, the introduction of the new feature is late on the various platforms. Mobile
CPU-intensive applications are mostly targeted at a native implementation because the new options provide you with the best performance.
Games are among the most apparent candidates for a native execution. Intensive game graphics processing is not sufficient for solutions
such as JavaScript. In a native approach, dynamic models of data objects that constantly alter should also be implemented. Graphs and
graphics for data replication can often be achieved with JavaScript, but the output begins to shock as the number of data points increases. If
a solution to make a thousand or more data points is necessary, a native compilation should be used. Every major platform offers a
guideline on the principles of best practice design. Android indicates that your menu should be put on the base of the screen. As iOS is
putting user menus on top of the show. These models are useful when designing applications that look and sound comfortable to the end
user. It allows them to feel like the app is not a foreign entity but an extension of the computer. In competing applications this will increase
user detention rates. Staying native to mobile devices also offers a stronger experience of touch interaction. Manipulations, pinches and
swipes work just as they should. The users would not be as disappointed with the content because of the intuitive or at least clear
responses on artifacts in the device.

Matched Source

No plagiarism found

You might also like