User Manual

Learn Web and Mobile Application Differences

19/12/25
In the application development process with Kuika, web and mobile applications have some differences in some points.
Learn Web and Mobile Application Differences

The development process of Web and Mobile applications in Kuika differs in terms of some features. These differences are based on the hardware, software features and user interactions of the platforms. In this training content, you will learn the differences between web and mobile applications.

Web and Mobile Application Differences

Web Applications

The web application type is basically responsive design and enables the development of applications that run on a browser. Web-based applications are usually accessible through internet browsers and are mostly used on desktop devices (PC, laptop). The Web application type does not have mobile features such as dialing a phone number or sharing with another application on the device. Instead, Web applications offer the user more features such as form-based interactions, web service connections, data visualizations, etc.

Mobile Applications

Mobile-friendly apps have features that work on both Android and iOS devices and take full advantage of the hardware and software capabilities of mobile devices. Mobile apps enable actions such as dialing a phone number, sending a message or sharing, while web apps do not. The mobile app development process allows for a single development for both platforms, which simplifies the development process.

Differences between Web and Mobile Application Types:

  1. Configuration Settings:
    • In web applications: Settings can only be made for the web platform.
    • In mobile compatible applications: You can configure settings for both web and mobile platforms.
  2. Element Differences:
    • In web apps: You can access all elements in web application type.
    • In mobile application type: Some elements such as Tooltip, Date&Time, Range are not available.
  3. Action Differences:
    • In web applications: For example, actions such as Read NFC, which allows you to transfer data wirelessly between devices, are not available.
    • In mobile applications: Actions are not available, for example, the Export Excel action, which is used to export a specific data set in Excel format.

Reasons for the Differences in Web and Mobile Application Types:

  1. List Screen Structure:
    • In web applications: List screens usually use page numberers.
    • In mobile applications: New content is loaded by scrolling on list screens. Thus, it offers a more suitable solution for the screen sizes and interaction style of mobile devices.
  2. Development Process:
    • Web application type: Tests are performed and optimized on different platforms to develop an application that can work on every device.
    • Mobile application type: A single development is done for both Android and iOS platforms. In this way, elements and actions are kept common for both devices and operating systems.

Action Differences

The table below specifies the system actions that work only in mobile apps or only in web apps. The actions have been specifically designed and rolled out according to each application's features and use cases.

Action Name Web Mobile
Param Payment Pay None Secure
Param Payment Pay 3D
Read NFC
Open In Web
Scan Devices
Saved Device Available
Is Connected
Forgot Device
Disconnect
Connect Bluetooth
Bluetooth Permission Is Given
Bluetooth Is Open
Update User Name
Run UI Vision Macro
Get User Task Summary
Get Process Registry List
Get My Tasks History
Update Stripe User Info
Import Excel Base64
Get Excel Base 64
Export Excel
Download VCF
Send Whatsapp Message
Get Component Base64
Download Report
Copy To Clipboard
Component to PDF

Element Differences Depending on Project Type

Kuika Low-code Platform provides most of the elements used in the development process (95%) common to both web and mobile-friendly application types. However, there are some minor differences depending on the device, operating system or user experience (UX) requirements of the application.

Although the same elements are generally used in both application types, there may be slight platform-specific differences in the properties of some elements. These differences are made specifically to optimize the user experience of the elements and adapt to the limitations of the platform.

Reasons for Element Differences:

  • Device Compatibility: Design and functionality optimization is done to adapt to the requirements of touch screens, smaller screen sizes and different operating systems on mobile devices.
  • Operating System Requirements: While web apps run on a browser, mobile apps run on operating systems such as Android and iOS. This can result in some elements only being available on certain platforms or working in different ways.
  • User Experience (UX): User experience in mobile apps focuses on touch features and faster interactions, while web apps prioritize a keyboard and mouse-friendly experience.

Examine Element Differences:

The below lists the elements in the Kuika Low-code Platform that are only available in web apps. These elements are optimized for web application specific needs and browser-based functionalities.

Apart from these web-only elements, all other elements can be used in both web and mobile-friendly applications. This is part of the flexible and user-friendly development environment Kuika offers.
  • MD Editor
  • Micro App
  • Divider
  • Big File Upload
  • Radio Group
  • Multi Select
  • Language Selector
  • Rate
  • Range Slider
  • Percent
  • Currency
  • Content menu
  • Button
  • Stepper
  • Collapse
  • Tree
  • Tooltip
  • Thumbnail
  • QR Renderer
  • Countup
  • Barcode Renderer
  • Month picker
  • Date time range
  • Date range
  • Pivot Table
  • Calendar
  • Process Automation
  • Gauge Chart

Screen Differences

On the Kuika platform, there are significant differences in screen templates and designs in the web and mobile application development process.

Master Screen Support:

  • In Web Applications: Master Screen support is available. Master Screen allows the overall structure and templates of the application to be managed on a central screen. This allows quick access to different parts of the application and provides a more organized user interface (UI).
  • In Mobile Applications: There is no Master Screen support. Mobile applications aim to offer a more flexible and user-friendly design by focusing on small screen sizes and portability requirements of mobile devices. Therefore, screen layouts in mobile apps are more simplified and functionally optimized.

Template Screens (Templates):

When creating a new screen, there are differences in template options between Web and Mobile app types. Templates are optimized for the needs of each application, while allowing applications to develop quickly and efficiently.

  • Web Applications: A wider range of templates is offered for Dashboard screens. It allows you to create more detailed and customizable interfaces for desktop users. The following templates are available in web application type:
    • Dashboard
    • Card and List
    • Two Columns
    • Three Columns
    • Marketing Dashboard
    • Marketing with Left Menu
    • Sales Dashboard
    • Sales Dashboard with Left Menu
  • Mobile Apps: Mobile app templates are simplified and designed to work more efficiently on mobile devices. Mobile screens are optimized for small screen sizes and touch interaction. Here are the templates available in mobile apps:
    • Dashboard
    • Card and List
    • Two Columns
    • Three Columns

Configuration Settings

Depending on the type of application you create, the configurations that will be used in the process of generating your application may differ. Configuration settings for web and mobile applications are independent of each other and are customized according to the requirements of each application.

Web Application Configurations:

Basic configurations are usually sufficient for web applications. When you create your application on the web platform, all necessary configurations are automatically determined and you only need to configure for the web. This allows the application to be quickly generated and tested.

Mobile Application Configurations (Android/iOS):

For mobile compatible applications, a more detailed configuration process is required. Separate configurations must be made for both Android and iOS platforms. Configurations are prepared to meet the different requirements of both operating systems.

  • For Android To test your app on Android devices, the necessary settings are made and the app is packaged for the Android platform.
  • For iOS: TestFlight integration is done for iOS devices and the application becomes testable for the iOS platform.

Preview and Test Processes:

Both platforms have default configuration settings that will allow you to preview the application you have created. This way, you can preview your app from the first moment you create it, packaged for web or Android devices. For mobile versions of your app, you can also test it on Android devices and review it on iOS devices via TestFlight.

Email Notification when the Application is Generated:

After completing the necessary configurations for Android and iOS, when you generate your app, an e-mail is sent to your user account. This email will include a link to preview the app via Appetize and the information you need to download and test it on your Android device. You will also receive a link to TestFlight to test the app on your iOS devices.

This process allows you to develop apps that are optimized for web and mobile platforms separately and makes it easy to test on both platforms.

Other Related Content

No items found.

Glossary

No items found.

Alt Başlıklar