Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

app looses state when I move to another app, or screen

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • app looses state when I move to another app, or screen

    Running my app through a browser page saved to my home screen. If I leave the app and go to another app when I return the app is open but I loose state, well actually the page refreshes and redirects to my index page which is the login UX. Is there a way to maintain the state of the app when leaving and returning?

  • #2
    Re: app looses state when I move to another app, or screen

    It's in the UX Properties : Persist Component State
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)

    Comment


    • #3
      Re: app looses state when I move to another app, or screen

      Thank you Pete!

      Comment


      • #4
        Re: app looses state when I move to another app, or screen

        A little confused about this, In a complex layout that involved multiple embedded UX components I assume you would need to select this property for every UX? Don't really understand what is occurring when leaving the app to say make a phone call, and then returning. The app is still open however it looses state refreshes and returns to my index page. What is happening when moving between apps. If someone could explain this better it would be helpful.

        Comment


        • #5
          Re: app looses state when I move to another app, or screen

          The videos concerning persisting state deal more with a disconnected app. I tried the IOS refresh app setting however my app is being run through a saved to home screen browser page (safari) not sure if that has any bearing on it functioning as an app? I tried the persist data settings however my app has a lot of embedded UX components, with list controls, and before I go crazy trying different local storage settings I want to make sure I am barking up the right tree. Again I am not trying to run the app disconnected I am just trying to be able to move it from the background to the foreground without it refreshing. If I view it in the background it appears intact but as soon as I tap it and bring it to the foreground it refreshes and returns to the index page with initial login component UX displayed. This would be annoying to the user moving between my app and say a phone call link, and then returning. Anyone else dealing with this? Is their a source to better explain this? I thought perhaps that I am just loosing the login cookie when the app is moved to the background but this is just a guess. Using a 6 plus, but this behavior happens on multiple apple devices. I am also using some javascript to prefill the login info.
          Last edited by bob9145; 10-18-2016, 12:40 AM.

          Comment


          • #6
            Re: app looses state when I move to another app, or screen

            I noticed that I can open the UX on an iphone it loads my initial login page, I move it to the background. Then tap to bring back to the foreground and it appears for a split second and then refreshes. I have not yet logged in, and the login page is set to persist state. Why is it refreshing? Is this an IOS thing, or is this a setting in my app?

            This is key to my user experience if they are working with a list and they are moving in an out of the app they aren't going to tolerate it.
            Have to solve this one
            Last edited by bob9145; 10-19-2016, 12:22 PM.

            Comment


            • #7
              Re: app looses state when I move to another app, or screen

              It seems that although the app appears open in the background that it actually closes and uses just a splash screen image of your app. so when you touch to bring to the foreground it just is reopening the app. This seems to be a limitation of using a Safari save to home screen icon to access your app? Does setting up your app to be able to run disconnected solve this problem? Is it a limitation of not going through the complete process of making it an official apple app? Is there a work around? The simple problem I am trying to overcome is the ability for the user to multitask through the app as I explained previously. I would think this would be a common requirement? I know that a lot of Alpha developers are not going through the formal app process and just running their app this way. Is this a bad way to deploy the app? For me this is just a stepping stone towards a more legitimate app, and eventually a app distributed via the app store. Any incite on this would be appreciated.

              One additional note: If I use Safari directly the app does not lose state and I can leave and return no problem. However the idea is to present my app as an app, and not a website. So this is not a good solution, and is a barrier towards quick convenient use of the app.
              Last edited by bob9145; 10-19-2016, 12:33 PM.

              Comment


              • #8
                Re: app looses state when I move to another app, or screen

                Contacted Alpha on this one. They pointed me towards the pre release build and the new Application Cache properties of the UX. So my understanding of their response is that the current build isn't capable of maintaining the state of your app when moved to the background of an apple device. At least not without additional improvisation?

                Along these lines I would like to make it possible to skip the login screen altogether. So once logged into the app the login process is behind the scenes, and when the user taps my app it goes straight to the app without the visible necessity to login every time. I noticed that most of my apps I use work this way.

                These 2 things seem like the very basics of user experience to me since an app that is cumbersome will be discarded, for one that is quick, and easy. Surprised with all the apps being created by Alpha developers that maintaining state of a app without focus, and easy invisible login aren't a very common requirement if not a necessity.

                If others have conquered these hurdles please share.

                A thank you to AA for getting back to me on this issue.
                Bob

                Comment


                • #9
                  Re: app looses state when I move to another app, or screen

                  There are Mobile Apps and there are web apps. A Mobile App is either native or pseudo native (ie PhoneGapBuild) where you have control over your environment and access to hardware, file systems, etc.

                  A web app is an app running in a browser. It can do a lot but is restricted by what the browser can do. Alpha's added some amazing features for web apps... with the Application Cache being a fantastic addition. Still... it's a web app.

                  Comment

                  Working...
                  X