App-Development, Cloud-Server and distribution to multi clients!

Cloud-Database.. (And many more...)

OK - It's just a computer at another location - so what is this blog post about?

It's about the next step form my last blogpost: Database and Server synchronization.

In many conversations with other developers, most of them want to build a mobile app that is kind of an Access Point to the data used by one or more  PC-Application(s).

At first - no Form from the Desktop App should be taken into the mobile App!

Designing a mobile App with a "smaller" UI, to achieve some of the basic functionalities that are necessary to handle the data, is not a big deal. If you are new to FMX, it just takes a while.

So how could you overcome the problem of not reinventing the wheel and perhaps reuse the work for the next App, too?

BTW: Thank you for reading my blog… This blogpost is again just for advertising my Firemonkey Development Kit. ;-)  (sorry, linked post -  is not translated, yet)

Best practice for the development of libraries like my FDK is as always: "Eat Your Own Dog Food".

And I can promise  -  I eat it every day! It saves me a lot of time and things are always easier.

The next version of the FDK would have some new plugins.

1. Simple ORM
   Just create a class with some Field-Attributes and you'll get a Database with a Table to store the Fields. (nested Tables are also supported, for multi entries like 1-n Bank accounts or 1-n communication - subtables )
2. CRUD IO
   You like the easy CREATE / READ / UPDATE / DELETE access of your data. Set some Class-Attributes and use the simple ORM model to build your application.
   An Easy SQL-Producer is included.
3. MVVM 2.5
   How to Access the Data? Just bind (in Code) the View to your ViewModel/Model (CRUD->ORM) class and you can easily display the Class from (1) on your View.
4. All your Events - PropertyChanged - are auto-connected with one line of code. You can multi-connect data to 1-n UI-Fields. Data->View, View-Data and Bidirectional, with optional converter functions. There is no need for a special UI-Component and there is nothing to drop onto your form. As described in this post.
5. Async Await
   Perhaps you know Async Await from C# - I have a "lite" Version for UI/Async/Threading tasks included.
6. Async Threading Command Queue
   The Threaded-Command Queue is for SQLite/Embedded Databases that can only handle one Thread/Connection at the time. Define your Data-Access-needs and just call them by Name. The Queue will handle all your calls one after another - or if you have some important stuff to do, you can call it prioritized.
7. JSONStore-Server
   A "just use it" Unit to store every data you like in JSON Format on your server database.
8. REST-JSONStore-Client
   To handle the JSONStore Server-Side you get the Units to handle all transfers/updates/locking/rebuild features to do your data-exchange with the Server or/and multi Clients. Of course, this module has the Async Threading Commands for the module (6) included doing everything in the background.

So what is the deal? My goal for mobile App creation was:
Create your UI - create your Classes - just set some Bindings and Field-Attributes. Nothing to drop on your form and nothing to set in the object-inspector!

Just write some uses and have fun...