Page 1 of 1

PcApp Standalone file for customers

Posted: Wed Aug 07, 2024 9:57 am
by Nico595
Hi,

I designed a small Standalone App for customers. It's a small GUI App deployed with the Wiki recommendations. Thank you for your very good examples and documentation.

I renamed the App and the Flowcode runtime with the "renameMe" runtime file. Work fine but I have a window with "Flowcode" mention when the standalone App start.

Can I do a single window around the GUI without "Flowcode" mention, in start of App and around the App ?
Also the window of the App have not a good size, the size of the window is not perfectly of the same size of the GUI.
The size of the window is not saved after out of the App. I want also replace the "Flowcode" logo at the top of the window by my logo.

Re: PcApp Standalone file for customers

Posted: Wed Aug 07, 2024 11:07 am
by Steve-Matrix
Thanks for the comments. I have added your suggestions to our list.

Re: PcApp Standalone file for customers

Posted: Wed Aug 07, 2024 11:26 am
by Nico595
Thank you Steve,

For me it's not a good news. No professional user can deployed a Software with your name or other company name in a start of their software.
Your software is a tool for Professional users. We can't do marketing for you even if I like your job.
Maybe keep this starting and this window only for free versions of Flowcode.

Re: PcApp Standalone file for customers

Posted: Wed Aug 07, 2024 12:58 pm
by BenR
Hello,

We will take your comments onboard, however I'm not sure about this statement.
No professional user can deployed a Software with your name or other company name in a start of their software.
Any games made with Unity or Unreal usually have a splash screen when loading a game showing the game engine and this is perfectly acceptable.

As for adding a personalised splash screen for professional users, that's one for Steve but I imagine it's not a trivial thing to add in.

Re: PcApp Standalone file for customers

Posted: Wed Aug 07, 2024 1:06 pm
by Steve-Matrix
I have some thoughts on this, but any customisation will need to happen in the runtime executable. For example, it could be that simply removing the majority of Flowcode branding from the runtime exe for professional users will be enough and then deployed apps would rely on customised branding within the deployed app itself.

Nicolas and I have exchanged a few PMs about this issue and hopefully we will find a suitable solution or compromise.