Jump to content

Starting database app development

Recommended Posts

I need some help /guidance / perhaps there is sample app out there......

What I have done in past is start witha CRM app in Delphi .  I want to recreate that.  From what I have read I need to setup a REST API server to provide the app data Whether a PHP app or a Node.js server.      I nned some help or a colaborator that can provide guidance or example on how to do this.    The app I am starting with is kind of a base app that I base all kinds of projects on so its something I don't mind sharing with other to learn from and possibly make better with some kind of basic reporting feature etc.... so others can benefit as well. can be documented and even tutorial videos made to show how an application can be built with the platform. 

Database is in Postgres (my preference but should not matter in the end)

Tables : Users ,  contact, notes, tasks

2 Forms :

1) Login form -  user , password   with forgot password reset option

2) Main form with menu and tab control  to  add/ search contacts, with tabbed interface  for notes, tasks etc...

3) pw reset form

4) vaious message dialogues

5) data export form to export data to a csv file 


This would be a great app and process as it could then be documented in document or series of videos to show case how it can be developed.


Link to post
Share on other sites
  • 2 weeks later...
  • Administrators

Sorry for only noticing this post now. I'd be happy to brain storm this with you. I've earlier done this kind of apps so, that the server side has been written in Delphi or Lazarus.

Basically, the server is the only one talking with the database.

Then you need a socket server or a http(s) server component, for the communication. Here you have two possibilities:

  1. http(s) server, which means that the client communicates with the server using standard http(s) GET and PUT. If you do this, you can start development by simply using a web browser to call the server. And once that works, you can then fire the same http urls from a SMS app. Pretty simple to do and enough if the server only responds to queries.
  2. WebSocket server, which means that you do a bit more to design the API. This one allows for the client to connect once to the server and keep the communication channel open. Hence, both the client and server can asynchronously send data to each other.


As an example, the new designer in the Smart Mobile Studio uses the WebSocket-approach. SMS's IDE uses Indy's WebSocket server, which can answer to both standard http/https queries and do WebSocket connections. So the SMS IDE is the "server" and the designer (written in SMS) is a client. But both can and need to send commands to each other as:

  • Selecting a component in the designer results in the client sending a SELECT-command to the IDE (server)
  • Changing component's property in IDE's Object Inspector results in the IDE (server) sending a CHANGE-command to the designer (client)
  • Moving a component in the designer results in the client sending a MOVE-command to the IDE
  • etc..

So both the client and the server read from the WebSocket and have their own commands that they are listening to.


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...