Android: Multi-threading UI and Database (Room)

Each time I need an application, I encounter that those publish never fit my needs. However, I am lucky! I can make them myself.

Recently, I decided to create an exercise app that fit my purpose. Therefore, I began developing for Android again.

A few months ago, my Microsoft Phone’s battery gave up and a massive deployment to production was coming which required me to be available; therefore, I purchased the first Android I could find. For those who wonder why I had a Microsoft Phone, I was developing apps using Universal Windows Platform using HTML5, JavaScript and the WinJS library. Pretty slick; however, there were bugs and poor designed features which made people drop the Windows Phone. No even Verizon Wireless support it. A shame

Anyways, you folk are not reading this post to listen to my poorly written stories but to find a solution to your problem such as dealing with messages as:

  • Only the original thread that created a view hierarchy can touch its views.
  • Cannot access database on the main thread since it may potentially lock the UI for a long period of time

These error messages are common when working with the UI and trying to do transactions with the database via Room.

In Short

For those who don’t have the time or patience here is the code I use more often from all the other solutions:

final Handler handler = new Handler();
(new Thread(new Runnable() {
    public void run() {
        // DO DATABASE TRANSACTION Runnable() {
            public void run() {
                // DO UI STUFF HERE.

Other Options

So far, this is the easier and straight forwards solution that have being working for me.

I tried with runOnUiThread:

runOnUiThread(new Runnable() {
    public void run() {
		// Run code here

Also, I used AsyncTask:

new DatabaseAsync().execute();

private class DatabaseAsync extends AsyncTask<Void, Void, Void>{
    protected void onPreExecute(){
        // Pre-operation here.

    protected Void doInBackground(Void... voids){
        //Perform database operations here.
        return null;

    protected void onPostExecute(Void aVoid){
        // Do UI operations here

And used combinations of Thread and runOnUiThread:

new Thread(new Runnable() {
    public void run() {
        // Database operation here
        try {
            runOnUiThread(new Runnable() {
                public void run() {
                    // UI operation here
        } catch (Exception ex) {

I even took a look into RxJava which is a “Java VM implementation of Reactive Extensions: a library for composing asynchronous and event-based programs by using observable sequences.”.


There are many ways to tackle this issue as you can see. The trick here is to understand how android handles threading and UI threading; however, such topics are for another post.


JavaScript: Executing synchronously

I am being ask this question often; therefore, I am posting the answer here.

Commonly there are those who wish to do a process that normally is asynchronously, such as performing AJAX operations in a synchronous fashion. There are a few ways to do this.

If you are coding in JS for NodeJS, then you can use the package async-waterfall, example:

  function readFile(callback) {
        fs.readFile('your_file.json', function (error, file) {
            if (error) {
            } else {
                callback(null, file);
    function processFile(file, callback){
        // Some code here
    ], function (error) {
        if (error) {
            // handle error made in readFile or processFile method 

Else, you can use promise chains which is part of Javascript, example:

    new Promise(function(resolve, reject) {
          reject("error message");
    }).then(function(result) {
      return processFile(result)    

Or, you can use async/await:


Great Idea, I wish I could Help You.

In the middle of the night, while sleeping, you got a great idea for a new app. You are excited and cannot wait to share it with your friend, the Amazing Developer. In the morning, you call your pal and arrange to meet for lunch. You met and shared your vision with great expectation that your companion becomes your partner; however, you find yourself being turned down. You should not be surprised. It was meant to happen. While your idea was great, you were not prepared to present it.

Developing an app is not just sitting down and coding until it happens. Many other aspects must be taken into account such as:

  • The user interface: how does the application look?
  • The user experience: how does the application behave when interacting with the user?
  • The application flow: How does it flow from the main page where the user can go inside the application?
  • The name: Does the name already exist?
  • The market research: Are there other applications like it already existing? What differentiates your application from them? What it is unique or enhanced?
  • The website: No application will be taken seriously if there is not a website for it.
  • Publishing your application: Is your application a website? Then, what hosting do you need? Is your application a mobile app? Then, what are the requirements to publish such an application? Is your application for a desktop? Which OS will it support? How are you going to sell it?
  • Social Network: Do you need a presence on social networks to promote your app?
  • The maintenance: Who is going to take care of it? How will customers reach you when trouble shows up?
  • Do I need to add an End User License Agreement? How about a Disclosure Agreement?

The list goes on, but do not despair. There is a way that you can increase your chances of success and it is by doing your homework prior to presenting your idea.

So… You got your idea. You have it in your mind. You know how it should work and why it is so great. However, let’s face it, you do not know how to do programming nor you have the intention to learn about it, then what can you do? Well, let us tackle down the things that you can do that do not require any programming skills to accomplish it.

Draw a storyboard. You only need a pencil, a ruler, an eraser, and paper. Lots of paper. The idea is to draw how the program would look and how the program should behave when interacting with the user. What will happen when the user presses the arrow button? What text will show up in the text area? Check out how other applications do it and pick what you like about them. No technical skill required for that!
Draw the website. You should use four colors. Black and white, plus two colors of your choice. Keep it simple. Browse through the internet and use other websites as inspiration to build yours. What sections will the website have? What text and pictures will those sections hold? What can the users do on your website?

Do some market research. Are there already applications out there that do the same? What will your application provide that they do not have? Does the name you wish to use already exist?

Do you require funds? Can you obtain them if you have to? How much funds do you think you will need?

Do you need to create a corporation? What kind of corporation it is?

What else can you do that does not require programming?

In short, you need to do more than just present your inspiration. Before you present your idea to your Friendly Neighborhood Developer, you should already have a lot of work done. Then, your friend can worry about making time to do the coding because you are already on top of things. Your associate does not have to spend time designing, researching and doing extra work. He or she will be more than willing to join you on your enterprise.



Express Gateway: Tips

Configuration: Order of Policies Matter

When working on Auth0, make sure that the order in which you set the pipelines’ policies matches the order in which the policies are listed:
Order of policies matter

Metrics: Use epimetheus or prom-client Package

You can use either prom-client or epimetheus.
Personally, I found easier to use the epimetheus package in Gateway Express:

'use strict';

const epimetheus = require('epimetheus');

module.exports = function (gatewayExpressApp) {
  epimetheus.instrument(gatewayExpressApp, {url: '/metrics'});

Something to considered is that some of the metrics display by epimetheus and prom-client differ.
For example, with epimetheus the http request duration are in milliseconds:

http_request_duration_milliseconds{quantile="0.01",method="get",path="/api/",cardinality="one",status="200"} 1

while in prom-client, the http request duration are in seconds:

http_request_duration_seconds_bucket{service="api",instance="api-3432dc43c4-h3eeg",le="0.005",path="/metrics",method="GET",apiVersion="1.0.0",status="200"} 466081


Express Gateway use express. I tried different swagger packages; however, the closest results was to display all the endpoints from the admin side of Express Gateway.
Then, I decided to check the code implemented in the restify-swagger-jsdoc and it did the trick. Here is the modified code:

'use strict';

const swaggerJSDoc = require("swagger-jsdoc");
const path = require("path");
const fs = require("fs");
const mime = require("mime-types");
const swaggerUiPath = path.dirname(require.resolve('swagger-ui'));
const publicPath = '/api'.replace(/\/+$/, '');

const swaggerSpec = swaggerJSDoc({
	swaggerDefinition: {
		info: {
			title: 'API documentation',
			version: '0.0.1',
			description: 'API documentation'
		host: undefined,
		basePath: '/',
		schemes: undefined,
		tags: []
	apis: [

module.exports = function (gatewayExpressApp) {

	gatewayExpressApp.get(`${publicPath}/swagger.json`, (req, res) =&amp;gt; {
		res.setHeader('Content-type', 'application/json');

	gatewayExpressApp.get(new RegExp(publicPath + '\/?$'), (req, res) =&amp;gt; {
		res.setHeader('Location', `${publicPath}/index.html`);

	gatewayExpressApp.get(new RegExp(publicPath + '\/(.*)$'), (req, res) =&amp;gt; {
		fs.readFile(path.resolve(swaggerUiPath, req.params[0]), (err, content) =&amp;gt; {
			if (err) {
				res.send(`File ${req.params[0]} does not exist`);
			if (req.params[0] === 'index.html') {
				let jsonFileUrl =  `${ ? 'https' : 'http'}`.concat('://').concat(`${}${publicPath}/swagger.json`); 
				content = new Buffer(content.toString().replace('url = ""', `url = "${jsonFileUrl}"`)); 
			const contentType = mime.lookup(req.params[0]); 
			if (contentType !== false) { 
				res.setHeader('Content-Type', contentType); 



Amazon’s Alexa Dev Conference (Denver, CO)

On April 12 of 2018, I went to Amazon’s Alexa Dev Conference at the Denver Marriott Tech Center in 4900 S Syracuse St., Denver, Colorado.

I meet with my friend and co-worker Matt Reddick.

The conference was nice. After doing the checking and obtained our badges, we got greeted by substantial breakfast which consisted of cooked ham, sausage, scramble eggs, and french toasts made with raising bread (I think).

We went over:

  • Introduction, a future projection and a general overview of Alexa’s related product and services.
  • Skill building basics such as Intent, Slots, handling request, AWS Lambda, and NodeJS.
  • AMAZON.LITERAL vs. AMAZON.SearchQuery Slot
  • Voice Design, conversation flow diagrams vs. frame diagrams, and Session Attributes.
  • New Alexa Skills Kit features, APIs, calling public APIs and Calling cloud services
  • Using AWS DynamoDB (vs. Session Attributes) and AWS IOT.

Part of the presentation required the participation of the audience which I found interesting.

At the end, there was a competition based on the Skill all participant created. The participation was optional.


ask new --template
ask deploy
ask simulate -l "EN-US" -t "start quiz game"

Skill Code Generator for Skill Builder Language Models

GitHub Links

Other Links