AppInventor: Connect ke MySQL

From OnnoWiki
Revision as of 17:42, 14 January 2024 by Onnowpurbo (talk | contribs) (Created page with "App Inventor 2 is a visual programming environment that allows you to create Android apps without writing code. However, direct connection to MySQL servers is not supported na...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

App Inventor 2 is a visual programming environment that allows you to create Android apps without writing code. However, direct connection to MySQL servers is not supported natively in App Inventor. To interact with a MySQL database from an App Inventor app, you typically need to use a web service as an intermediary.

Here's a basic outline of the process:

Set Up a Web Service: You need a server-side script that can interact with your MySQL database. You can use a server-side language like PHP, Python, or Node.js for this purpose. This script will handle the database operations and communicate with your App Inventor app.

Example PHP script (api.php):

<?php
$servername = "your_mysql_server";
$username = "your_mysql_username";
$password = "your_mysql_password";
$dbname = "your_database_name";

// Create connection
$conn = new mysqli($servername, $username, $password, $dbname);

// Check connection
if ($conn->connect_error) {
    die("Connection failed: " . $conn->connect_error);
}
// Your database operations go here

$conn->close();
?>

Deploy the Web Service: Upload the PHP script to a web server with PHP support.

App Inventor Components: In your App Inventor project, use the Web component to send HTTP requests to your PHP script.

App Inventor Blocks: Use the Web component blocks to send requests to your web service. For example, you might use the Web.Get block to retrieve data from the server.

Example blocks for a simple GET request:

Adjust the URL to point to your deployed PHP script.

Remember, this is just a basic example. Depending on your application, you may need to handle more complex scenarios, like sending parameters, handling responses, error checking, and security considerations.

Also, note that direct database connections from a mobile app are generally not recommended due to security concerns. It's safer to use a web service as an intermediary to control and secure the interaction with your database.