5 of the Best Websites to Create Your Own Android Apps without Coding

Source: https://www.maketecheasier.com/create-an…8Make+Tech+Easier%29
Capture Date: 16.09.2018 22:56:06

Have you ever wished you could create an app? Maybe you want one for your business or just for yourself? Apps are not only useful for all kinds of business situations but in day-to-day activities as well. For example, you could make an app to help plan a wedding or other event. Only a few people would need it.

There are a seemingly unlimited number of websites promising an easy way to make apps. Most of them will be fronted with the word “free.” And to be fair, most of them are free to start. After that is when it changes. Depending on your need for the app, whether for your business or party planning, your budget may not allow for an expensive app or a substantial monthly commitment.

So if you’re not looking to make a million dollars from your app (or spend a boatload of money to create it), these five sites will allow you to create your own Android apps and still have money in your pocket when it’s complete.

1. Andromo

Andromo is the most popular Android app-maker platform.


It only require three steps to create your own app:

  1. Create an Andromo project.
  2. Fill out a few simple forms to add features, graphics, content and whatever makes your app unique.
  3. Click a button to build your app.

Unlike many of the other app builders, Andromo does not have a preview screen for you to see what your app will look like while adding items or changing formatting. After you create your app, they will email it to you. They do not support uploading of the app to the Play store. For free, you can create one app with ads. If you upgrade to the lowest cost plan for $8 a month, you can have up to fifty apps and monetize them.

2. AppsGeyser


AppsGeyser is totally free. They boast no fees, charges, subscription plans, or limits. There are over fifty different available templates to get you started and make creating the app even easier. The site uses a preview screen to show what your app looks like, but I had a little trouble getting that to work consistently. Because it’s free, they don’t support the publishing of the app to the stores. They will get fifty percent of any monetization you do to make up for the cost.

3. AppMachine


On the surface when you look at pricing, AppMachine seems more expensive, but you only need to pay if you plan on publishing the app to Google Play or another platform. There are 92 different templates available to choose from to begin making your app and a preview screen to keep up with the changes you make. They make it easier to imagine what you can place on a screen by comparing the building of the app to building with Legos. When you want to test out the app, they give you a QR code to scan which then opens it on your phone.

4. AppMakr


Appmakr charges $2 a month to have an app in the AppMakr market with their branding on the app. There is a free plan allowing you to publish mobile websites, but to have an app, you need at least that basic plan. Use their drag-and-drop interface and the preview pane to make as many apps as you want to for free. You choose a plan only when you decide to promote or publish an app. If you are only interested in creating an app to share with coworkers or friends, you can’t beat the price. It has tech support, a stats dashboard, and no charges or time limits for changes.

5. AppyPie


AppyPie has a straightforward user interface with a preview screen which allows you to drag and drop items onto your app and see the results. They also offer video tutorials to help you along as you create a Progressive Web App (PWA), not an Android. They do have a free plan that only allows you forty-eight hours to edit your app. The next plan jumps to $15 per month to create Android apps. AppyPie branding is on every app unless you are using the highest-priced plan.

How would an app that you design, just for your needs, make something in your life better? Give one of these sites a try and see if you can make it a reality.

Image credit: Closeup of designers creating mobile app prototype by baranq/Shutterstock

Managing API Keys

Source: https://www.learnhowtoprogram.com/androi…ts/managing-api-keys
Capture Date: 03.07.2018 21:28:06

In the previous lesson we acquired the secret access token we’ll use to request information from the Yelp Fusion API. But as you know, API keys, tokens, and credentials should not be stored directly in source code pushed to GitHub. This simply isn’t secure; especially if the API has a rate limit, charges for use, or provides access to sensitive information. We don’t want others obtaining our credentials!

Thankfully we can easily conceal our API keys, similar to what we did in JavaScript. The process is a tad different in Android, but we think you’ll get the hang of it quickly. In this lesson we’ll discuss how to obfuscate API credentials in Android apps, as we walk through integrating our Yelp access token into MyRestuarants. Once our API key is safely integrated we’ll begin constructing our first API call in upcoming lessons.

Hiding API Keys

1. Add Credentials to gradle.properties

First, we’ll add our new token the gradle.properties file located in the root directory. gradle.properties is simply a file where properties and configuration settings for gradle-built projects reside.



We must include a space between Bearer and the access token itself. And the term Bearer must be capitalized. This format looks a little funny compared to API credentials you’ve likely seen in the past, but it’s simply what this particular API requires. If we don’t follow this exact format, we won’t be able to successfully retrieve data.

2. Ignore gradle.properties

Next, let’s hide our gradle.properties file from GitHub by adding it to .gitignore so that the credentials we just listed will not be pushed to Github:


*.iml ... /gradle.properties

If you don’t see a .gitignore file in your project’s directory, you may have to switch from Android view to Project view in Android Studio. The Android view displays only the key source files of an Android project, whereas Project displays all files.


If you’ve already committed gradle.properties file to your Git repository you’ll have to retroactively remove it in order to begin ignoring it moving forward. To remove files listed in r .gitignore from your local repository, run the following command:

$ git rm --cached -r .

This will reset which files are staged for committing. You should be able to run $ git status, and see that all files are unstaged (including gradle.properties). After this, you can $ git add . and $ git commit -m "your commit message" again, and your new commit should not contain gradle.properties. For more details, check out the Removing Ignored Files from a Project section in this Java lesson.

3. Initialize String Constants

Next we’ll create a class to contain references to our Yelp credentials. Right-click on the primary package containing our source code and select New > Java Class. Name this new class Constants.java:


Within this file we’ll include the following code referencing the access token from gradle.properties:


public class Constants { public static final String YELP_TOKEN = BuildConfig.YELP_TOKEN; }

Here, we’re instructing the application that the value for our YELP_TOKEN constant can be found in the BuildConfig file. BuildConfig.java is a file that is generated automatically when gradle builds our project. You’ll likely receive an error when you add the code above. But that’s alright, this is simply because we haven’t added YELP_TOKEN to our Build Config yet. We’ll do this next.

4. Connect Credentials When the Project Builds

Next, let’s instruct our application to include our token in the BuildConfig file when it is created. We’ll add the following to our build.gradle file:

build.gradle(Module: app)

apply plugin: 'com.android.application' android { ... buildTypes.each { it.buildConfigField 'String', 'YELP_TOKEN', YelpToken } }

Here we’re instructing our application to include the token placed in gradle.properties in the BuildConfig file when it is built. The keys in our Constants.java class will now refer to the strings added to gradle.properties at runtime. And none of our credentials will be visible on GitHub!