3 ms·

You have to tell us what is wrong first, in other words why do you think you're going wrong? There is nothing wrong with what you've described as far as I can t

You have to tell us what is wrong first, in other words why do you think you're going wrong? There is nothing wrong with what you've described as far as I can tell. But what issues are you having? Users not going to your site? Likely not a tech problem.

graycat 10y ago
Thanks. My site is not live on the Internet yet. On my development computer, it appears that the site works as intended, but I'm still testing, say, alpha testing. Then when I invite in people, call that beta testing. For what is "wrong", I am just guessing that I might have encountered some of the problems mentioned in the OP. Or, maybe even the simple, old HTML, CSS, and JavaScript I'm sending to the users might have problems on some Web browsers on some mobile devices? I don't have a mobile device, certainly not a big collection of them, for testing. So, likely the beta test will be the first real test if my simple, old HTML, etc. will work on various Web browsers on iPhone, Android, tablets, old/new laptops, etc. But no doubt other Web site developers here on HN have already been there, done that. Or, for the question, what precautions, considerations, limitations, etc. have to honor to have a relatively simple Web page display and act as intended on a wide range of client devices? Thanks!
- deleted 10y ago
  [deleted]
- deleted 10y ago
  [deleted]
- elliotec 10y ago
  As long as the people developing your site have been keeping up with things since the mobile web became a thing (several years), it should be expected that they can develop an app that functions well on just about any device that will run it. This is common, required knowledge of developers. They should be testing the site on as many devices as possible, and developing it with cross-browser capabilities in mind and tooling that does it for them. You can check yourself to see if it works There is no excuse for not being able to develop a consistent experience across as many devices as possible. And it sounds like the poor OP just got a lazy developer.
  - graycat 10y ago
    Except in this case, the developer is me, and this is my first Web site!
    - elliotec 10y ago
      Ok, then you need to learn the things I mentioned. It is not as hard as OP suggests. Based on your comment history, you seem more than capable of figuring this out.
      - graycat 10y ago
        Thanks. From the reactions here, it seems that my initial guesses were correct or nearly so -- for really simple HTML, CSS, controls, no ambiguity about the layout, and nearly no JavaScript, what I'm sending will work well enough on nearly any Web browser nearly all the time. At least for now in my testing, I will assume that is so and, thus, leave testing on relatively unpopular Web browsers for much later, likely after I go live. Thanks; I just slimmed down the alpha testing!

graycat 10y ago

Thanks. My site is not live on the Internet yet. On my development computer, it appears that the site works as intended, but I'm still testing, say, alpha testing. Then when I invite in people, call that beta testing. For what is "wrong", I am just guessing that I might have encountered some of the problems mentioned in the OP. Or, maybe even the simple, old HTML, CSS, and JavaScript I'm sending to the users might have problems on some Web browsers on some mobile devices? I don't have a mobile device, certainly not a big collection of them, for testing. So, likely the beta test will be the first real test if my simple, old HTML, etc. will work on various Web browsers on iPhone, Android, tablets, old/new laptops, etc. But no doubt other Web site developers here on HN have already been there, done that. Or, for the question, what precautions, considerations, limitations, etc. have to honor to have a relatively simple Web page display and act as intended on a wide range of client devices? Thanks!

deleted 10y ago
[deleted]
deleted 10y ago
[deleted]
elliotec 10y ago
As long as the people developing your site have been keeping up with things since the mobile web became a thing (several years), it should be expected that they can develop an app that functions well on just about any device that will run it. This is common, required knowledge of developers. They should be testing the site on as many devices as possible, and developing it with cross-browser capabilities in mind and tooling that does it for them. You can check yourself to see if it works There is no excuse for not being able to develop a consistent experience across as many devices as possible. And it sounds like the poor OP just got a lazy developer.
- graycat 10y ago
  Except in this case, the developer is me, and this is my first Web site!
  - elliotec 10y ago
    Ok, then you need to learn the things I mentioned. It is not as hard as OP suggests. Based on your comment history, you seem more than capable of figuring this out.
    - graycat 10y ago
      Thanks. From the reactions here, it seems that my initial guesses were correct or nearly so -- for really simple HTML, CSS, controls, no ambiguity about the layout, and nearly no JavaScript, what I'm sending will work well enough on nearly any Web browser nearly all the time. At least for now in my testing, I will assume that is so and, thus, leave testing on relatively unpopular Web browsers for much later, likely after I go live. Thanks; I just slimmed down the alpha testing!