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



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

Fully Offline Application

  • Filter
  • Time
  • Show
Clear All
new posts

  • Fully Offline Application

    Hi all,

    I know this is probably impossible to do but thought I would put it out their anywhere. Is their anyway a mobile login can validate against a server with limited/no mobile phone connection.

    I'm asking this as our clients who are using our mobile application work in area with very very poor mobile signal and have no access at all. When they do login in the mornings they usually do connected to wifi and get in quick, but this is then the last time a connection is possible or strong enough to connect. So when the app closes or is shut down they can no longer log straight back into to the application.

    Is an offline mobile log in possible in any way?

  • #2
    Re: Fully Offline Application

    Login in the strictest sense? No. You have no server to log in to. But, since you've logged in once and verified your user, you can then use the device filesystem to store username and password information. Check for a connection during the next login and if it's there use it. If no connection, grab the stored info and compare the entered info against it. In some Apps I've auto logged in users. In other Apps I retrieve and set the username so they don't have to enter it all the time... just enter the password.

    The UX has a number of .phoneGap methods. I use these to store and retrieve user data including login data.


    • #3
      Re: Fully Offline Application

      Hi David,

      Thanks for the reply. Yeah I was wondering If I could use the cached info that the user enters already to then redirect them to a cached form/object that could be in the background and be present when the connection is not available.

      Are their any demos that you know of where this sort of login method is present?


      • #4
        Re: Fully Offline Application

        Ollie, now that you're writing about "cache" I'm wondering what type of application you're running. Web app running on a mobile device in a browser? Or an installed, native(ish) PhoneGap Build Mobile app?


        • #5
          Re: Fully Offline Application


          Its a Phonegap build app not a browser which is making me think that the cached memory cant be used?


          • #6
            Re: Fully Offline Application

            Ok... good... then cache has nothing to do with the process. Have a look in the current release notes for PhoneGap - File Systems Actions. Also look for PhoneGap - File System Methods. There are a lot of these and they allow very fine control over what you'd like to do.

            Depending on your devices, you could use the Fingerprint Scanner plugin... search for that in the release notes as well.

            Although many devices do incorporate fingerprint scanners... many do not... so going with the .phoneGap methods may be better at this point.

            You want to store your username and password in a local file in the device file system. The .phoneGap file methods let you do this.

            There are a lot of .phoneGap file methods. You'd use the client-side event onPhoneGapReady to start the process and see if your "security" file (call it whatever you like) exists. If it does exist, then read it. It will be just JSON so you can then extract your username and password and, if they have values, assign them to dialog namespace variables.

            Now you've got the last person who logged in.

            Next you'd transition to the login panel and have the user log in. But, the login button checks for a connection. If there is one, then all is good and you can log in normally. If there isn't a connection then compare what the user entered against what you pulled from the local file system. If they match then transition to your application panel.

            Whenever the user logs in "normally" you'd use the client-side afterLogin event to write the credentials to the device file system using the .phoneGap file methods.