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

Splitting a large UX into smaller components

  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Re: Splitting a large UX into smaller components

    It's very easy for things to get lost in translation in a product in constant revision ( a good thing ).

    Stick with it and you will get the rewards.
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)


    • #17
      Re: Splitting a large UX into smaller components

      If your goal is to create an app your client can use on a plane, disconnected, then that's what you should work on... and toward. As Pete shows, building a connected application that delivers 500 rows at a time is very responsive. 1 million, 2 million, doesn't really matter since the sql backend is doing the work responding to a request by Alpha for 500 rows. Whether it's the first page or last page of a million rows... you're asking for 500 rows... so it will always be fast. The search, as shown, is server-side, so if you're returning a small number of rows it's going to be fast as well.

      Overall, you have to be very, very specific about what your development goals and plans are... what you want to deliver... what you need to deliver. And then build toward those goals.

      You can't have a disconnected application and have 500 rows at a time as totally acceptable... the 2 don't go together.

      There are at least 4 disconnected, large data solutions available for Alpha including File System Storage via Alpha, SQLite and noSQL.
      Last edited by Davidk; 07-17-2016, 10:10 PM.


      • #18
        Re: Splitting a large UX into smaller components

        Well said David.
        Insanity: doing the same thing over and over again and expecting different results.
        Albert Einstein, (attributed)
        US (German-born) physicist (1879 - 1955)


        • #19
          Re: Splitting a large UX into smaller components

          Hi, David I fully understand and agree.

          I had set myself the goal of making the connected web app have full functionality. The disconnected app was never going to have a mapping element. My agreed development route was to offer a number of "experiments" , an experiment can be less polished and just show the layout and functionality.

          The task I set myself was searchable "horizontals" with a full filter functionality. The "verticals" had no real meaning if there were not 4 750ml bottles of different years. This reduces the list to 500 lines. With verticals, it was worth having mapping and bottle labels just to give the page a little more interest.

          The client was not very interested in a dashboard, the wine is fairly static. Equally, he did not want to have a pretty landing page.

          One important function was to check the average and last price paid for a particular wine. This would generally be done on the iPhone 6.

          So as you can see a fairly simple application, the skin needs to be consistent across all devices whether offline or online.

          Producing a working app is say 40% of the project. It also needs to be fit for purpose in every use case. The last 40% is the UX/UI design and this is also causing me problems because of the way the French Laundry works.

          I am just sitting down to study Pete's video again.

          Thanks Guys.


          • #20
            Re: Splitting a large UX into smaller components

            These Video's might help you..

            Video on some tricks.

            Video on background Images and opacity.
            Insanity: doing the same thing over and over again and expecting different results.
            Albert Einstein, (attributed)
            US (German-born) physicist (1879 - 1955)


            • #21
              Re: Splitting a large UX into smaller components

              Thanks Pete