Responsive UI design using Appcelerator Titanium framework












2















I am new in Appcelerator framework, I have developed one application in appcelerator, but that application looks good on IOS but for android its not look good.
I want to develop a screen which is responsive like html.
Is there any way to design appcelerator screen like responsive screen.



Thanks you.






responsive-design titanium appcelerator appcelerator-titanium







share|improve this question





























    2















    I am new in Appcelerator framework, I have developed one application in appcelerator, but that application looks good on IOS but for android its not look good.
    I want to develop a screen which is responsive like html.
    Is there any way to design appcelerator screen like responsive screen.



    Thanks you.






    responsive-design titanium appcelerator appcelerator-titanium







    share|improve this question



























      2












      2








      2








      I am new in Appcelerator framework, I have developed one application in appcelerator, but that application looks good on IOS but for android its not look good.
      I want to develop a screen which is responsive like html.
      Is there any way to design appcelerator screen like responsive screen.



      Thanks you.






      responsive-design titanium appcelerator appcelerator-titanium







      share|improve this question
















      I am new in Appcelerator framework, I have developed one application in appcelerator, but that application looks good on IOS but for android its not look good.
      I want to develop a screen which is responsive like html.
      Is there any way to design appcelerator screen like responsive screen.



      Thanks you.






      responsive-design titanium appcelerator appcelerator-titanium




      responsive-design titanium appcelerator appcelerator-titanium






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 15 '18 at 12:34









      Rene Pot

      21k45885




      21k45885










      asked Nov 15 '18 at 12:10









      Pravin AbhalePravin Abhale

      8627




      8627
























          1 Answer
          1






          active

          oldest

          votes


















          2














          Don't define width, unless calculated. iOS is fairly simple with only a handful different resolutions, on Android you never know what resolutions you might encounter.



          Luckily, you can specify widths differently in Titanium than you can in HTML. For example



          var view = Ti.UI.createView({
          
  left: 20,
          
  right: 20
          
});


          This will make your view the width of the parent, with 20 padding right and left, the width will be calculated.



          Also, always stick to native UI elements. So tabgroups, actionbar/navigationBar should all be used so you don't have to worry about cross platform support, styling and sizing of those elements.



          Furthermore, most view should be put in ScrollView's when you don't know how tall the UI is going to be. It could fit on iOS, but not on a small Android device. Putting it in a scrollview will always fix the screen as the scrollview will automatically enable scrolling when the content is taller than what fits.



          So conclusion




          • Width should be defined relative. Either with left/right properties, or calculated

          • If height of content is not yet known or not designed to be fullscreen wrap it in a scrollview

          • Stop thinking of apps as websites, start thinking of them as Apps. Layout works differently


          Lastly, Appcelerator is the company, Titanium is the technology you're using :)






          share|improve this answer
























          • Thank you Pot for your reply, i have tried the approch which you provided. but i m struggling with width, because i have 4 element in a row it works fine for iPhone 7 or more but when app runs on smaller device that 4 elemtent dosent get enough space and its not clickable, what i want is if width is not enoug then it works as a flow layout, that can come in the next row instead of single row. Thank you in advance

            – Pravin Abhale
            Nov 16 '18 at 7:08






          • 1





            for that you can try to put all 4 views in a parentView with layout:'horizontal and put parentView's height:Ti.UI.SIZE. can you share some code or screenshot of your problem

            – Swanand
            Nov 16 '18 at 11:29











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53319221%2fresponsive-ui-design-using-appcelerator-titanium-framework%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          Don't define width, unless calculated. iOS is fairly simple with only a handful different resolutions, on Android you never know what resolutions you might encounter.



          Luckily, you can specify widths differently in Titanium than you can in HTML. For example



          var view = Ti.UI.createView({
          
  left: 20,
          
  right: 20
          
});


          This will make your view the width of the parent, with 20 padding right and left, the width will be calculated.



          Also, always stick to native UI elements. So tabgroups, actionbar/navigationBar should all be used so you don't have to worry about cross platform support, styling and sizing of those elements.



          Furthermore, most view should be put in ScrollView's when you don't know how tall the UI is going to be. It could fit on iOS, but not on a small Android device. Putting it in a scrollview will always fix the screen as the scrollview will automatically enable scrolling when the content is taller than what fits.



          So conclusion




          • Width should be defined relative. Either with left/right properties, or calculated

          • If height of content is not yet known or not designed to be fullscreen wrap it in a scrollview

          • Stop thinking of apps as websites, start thinking of them as Apps. Layout works differently


          Lastly, Appcelerator is the company, Titanium is the technology you're using :)






          share|improve this answer
























          • Thank you Pot for your reply, i have tried the approch which you provided. but i m struggling with width, because i have 4 element in a row it works fine for iPhone 7 or more but when app runs on smaller device that 4 elemtent dosent get enough space and its not clickable, what i want is if width is not enoug then it works as a flow layout, that can come in the next row instead of single row. Thank you in advance

            – Pravin Abhale
            Nov 16 '18 at 7:08






          • 1





            for that you can try to put all 4 views in a parentView with layout:'horizontal and put parentView's height:Ti.UI.SIZE. can you share some code or screenshot of your problem

            – Swanand
            Nov 16 '18 at 11:29
















          2














          Don't define width, unless calculated. iOS is fairly simple with only a handful different resolutions, on Android you never know what resolutions you might encounter.



          Luckily, you can specify widths differently in Titanium than you can in HTML. For example



          var view = Ti.UI.createView({
          
  left: 20,
          
  right: 20
          
});


          This will make your view the width of the parent, with 20 padding right and left, the width will be calculated.



          Also, always stick to native UI elements. So tabgroups, actionbar/navigationBar should all be used so you don't have to worry about cross platform support, styling and sizing of those elements.



          Furthermore, most view should be put in ScrollView's when you don't know how tall the UI is going to be. It could fit on iOS, but not on a small Android device. Putting it in a scrollview will always fix the screen as the scrollview will automatically enable scrolling when the content is taller than what fits.



          So conclusion




          • Width should be defined relative. Either with left/right properties, or calculated

          • If height of content is not yet known or not designed to be fullscreen wrap it in a scrollview

          • Stop thinking of apps as websites, start thinking of them as Apps. Layout works differently


          Lastly, Appcelerator is the company, Titanium is the technology you're using :)






          share|improve this answer
























          • Thank you Pot for your reply, i have tried the approch which you provided. but i m struggling with width, because i have 4 element in a row it works fine for iPhone 7 or more but when app runs on smaller device that 4 elemtent dosent get enough space and its not clickable, what i want is if width is not enoug then it works as a flow layout, that can come in the next row instead of single row. Thank you in advance

            – Pravin Abhale
            Nov 16 '18 at 7:08






          • 1





            for that you can try to put all 4 views in a parentView with layout:'horizontal and put parentView's height:Ti.UI.SIZE. can you share some code or screenshot of your problem

            – Swanand
            Nov 16 '18 at 11:29














          2












          2








          2







          Don't define width, unless calculated. iOS is fairly simple with only a handful different resolutions, on Android you never know what resolutions you might encounter.



          Luckily, you can specify widths differently in Titanium than you can in HTML. For example



          var view = Ti.UI.createView({
          
  left: 20,
          
  right: 20
          
});


          This will make your view the width of the parent, with 20 padding right and left, the width will be calculated.



          Also, always stick to native UI elements. So tabgroups, actionbar/navigationBar should all be used so you don't have to worry about cross platform support, styling and sizing of those elements.



          Furthermore, most view should be put in ScrollView's when you don't know how tall the UI is going to be. It could fit on iOS, but not on a small Android device. Putting it in a scrollview will always fix the screen as the scrollview will automatically enable scrolling when the content is taller than what fits.



          So conclusion




          • Width should be defined relative. Either with left/right properties, or calculated

          • If height of content is not yet known or not designed to be fullscreen wrap it in a scrollview

          • Stop thinking of apps as websites, start thinking of them as Apps. Layout works differently


          Lastly, Appcelerator is the company, Titanium is the technology you're using :)






          share|improve this answer













          Don't define width, unless calculated. iOS is fairly simple with only a handful different resolutions, on Android you never know what resolutions you might encounter.



          Luckily, you can specify widths differently in Titanium than you can in HTML. For example



          var view = Ti.UI.createView({
          
  left: 20,
          
  right: 20
          
});


          This will make your view the width of the parent, with 20 padding right and left, the width will be calculated.



          Also, always stick to native UI elements. So tabgroups, actionbar/navigationBar should all be used so you don't have to worry about cross platform support, styling and sizing of those elements.



          Furthermore, most view should be put in ScrollView's when you don't know how tall the UI is going to be. It could fit on iOS, but not on a small Android device. Putting it in a scrollview will always fix the screen as the scrollview will automatically enable scrolling when the content is taller than what fits.



          So conclusion




          • Width should be defined relative. Either with left/right properties, or calculated

          • If height of content is not yet known or not designed to be fullscreen wrap it in a scrollview

          • Stop thinking of apps as websites, start thinking of them as Apps. Layout works differently


          Lastly, Appcelerator is the company, Titanium is the technology you're using :)







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 15 '18 at 12:33









          Rene PotRene Pot

          21k45885




          21k45885













          • Thank you Pot for your reply, i have tried the approch which you provided. but i m struggling with width, because i have 4 element in a row it works fine for iPhone 7 or more but when app runs on smaller device that 4 elemtent dosent get enough space and its not clickable, what i want is if width is not enoug then it works as a flow layout, that can come in the next row instead of single row. Thank you in advance

            – Pravin Abhale
            Nov 16 '18 at 7:08






          • 1





            for that you can try to put all 4 views in a parentView with layout:'horizontal and put parentView's height:Ti.UI.SIZE. can you share some code or screenshot of your problem

            – Swanand
            Nov 16 '18 at 11:29



















          • Thank you Pot for your reply, i have tried the approch which you provided. but i m struggling with width, because i have 4 element in a row it works fine for iPhone 7 or more but when app runs on smaller device that 4 elemtent dosent get enough space and its not clickable, what i want is if width is not enoug then it works as a flow layout, that can come in the next row instead of single row. Thank you in advance

            – Pravin Abhale
            Nov 16 '18 at 7:08






          • 1





            for that you can try to put all 4 views in a parentView with layout:'horizontal and put parentView's height:Ti.UI.SIZE. can you share some code or screenshot of your problem

            – Swanand
            Nov 16 '18 at 11:29

















          Thank you Pot for your reply, i have tried the approch which you provided. but i m struggling with width, because i have 4 element in a row it works fine for iPhone 7 or more but when app runs on smaller device that 4 elemtent dosent get enough space and its not clickable, what i want is if width is not enoug then it works as a flow layout, that can come in the next row instead of single row. Thank you in advance

          – Pravin Abhale
          Nov 16 '18 at 7:08





          Thank you Pot for your reply, i have tried the approch which you provided. but i m struggling with width, because i have 4 element in a row it works fine for iPhone 7 or more but when app runs on smaller device that 4 elemtent dosent get enough space and its not clickable, what i want is if width is not enoug then it works as a flow layout, that can come in the next row instead of single row. Thank you in advance

          – Pravin Abhale
          Nov 16 '18 at 7:08




          1




          1





          for that you can try to put all 4 views in a parentView with layout:'horizontal and put parentView's height:Ti.UI.SIZE. can you share some code or screenshot of your problem

          – Swanand
          Nov 16 '18 at 11:29





          for that you can try to put all 4 views in a parentView with layout:'horizontal and put parentView's height:Ti.UI.SIZE. can you share some code or screenshot of your problem

          – Swanand
          Nov 16 '18 at 11:29




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53319221%2fresponsive-ui-design-using-appcelerator-titanium-framework%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          -

          Popular posts from this blog

          Florida Star v. B. J. F.

          Image
          Florida Star v. B. J. F. From Wikipedia, the free encyclopedia Jump to navigation Jump to search United States Supreme Court case Florida Star v. B. J. F. Supreme Court of the United States Argued March 21, 1989 Decided June 21, 1989 Full case name The Florida Star v. B. J. F. Citations 491 U.S. 524 ( more ) 109 S. Ct. 2603; 105 L. Ed. 2d 443; 1989 U.S. LEXIS 3120; 57 U.S.L.W. 4816; 16 Media L. Rep. 1801 Prior history The Florida Star v. B.J.F., 530 So.2d 286 (1988) Supreme Court of Florida; Florida Star v. B.J.F., 499 So.2d 883 (1986) Fla. Dist. Court of Appeals Holding Florida Stat. § 794.03 is unconstitutional to the extent it makes the truthful reporting of information that was a matter of public record unlawful, as it violates the First Amendment. Court membership Chief Justice William Rehnquist Associate Justices William J. Brennan Jr.  · Byron White Thurgood Marshall  · Harry Blac...
          Read more

          Danny Elfman

          Image
          Danny Elfman From Wikipedia, the free encyclopedia Jump to navigation Jump to search Danny Elfman Elfman at the 2010 San Diego Comic-Con Born Daniel Robert Elfman ( 1953-05-29 ) May 29, 1953 (age 65) Los Angeles, California, U.S. Spouse(s) Bridget Fonda ( m.  2003) Children 1 Musical career Genres Rock [1] ska [2] new wave film music video game music Occupation(s) Composer, singer, songwriter, record producer Instruments Trombone guitar percussion vocals keyboards [3] Years active 1972–present Associated acts Oingo Boingo James Newton Howard Daniel Robert Elfman (born May 29, 1953) is an American composer, singer, songwriter, and record producer. Elfman first became known for being the lead singer and songwriter for the band Oingo Boingo from 1974 to 1995. He is well known for scoring films and television shows, particularly his frequent collabora...
          Read more

          Lugert, Oklahoma

          Image
          Unincorporated community in Oklahoma, United States Lugert, Oklahoma Unincorporated community Foundations from the town of Lugert at the bottom of Lake Altus-Lugert Lugert, Oklahoma Location within the state of Oklahoma Coordinates: 34°53′45″N 99°16′31″W  /  34.89583°N 99.27528°W  / 34.89583; -99.27528 Coordinates: 34°53′45″N 99°16′31″W  /  34.89583°N 99.27528°W  / 34.89583; -99.27528 Country United States State Oklahoma County Kiowa Time zone UTC-6 (Central (CST))  • Summer (DST) UTC-5 (CDT) GNIS feature ID 1100597 Lugert is an unincorporated community in Kiowa County, Oklahoma. [1] The town of Lugert was founded in 1901 on 80 acres (320,000 m 2 ). In the town, there was a general store that housed the Post office and sold dry goods, school supplies, groceries, harnesses, axes and much more. It was named for Frank Lugert, who had moved to the area in 1898. Lugert owned land where the town was sited and also owned the general st...
          Read more