CA3LE, on 06 October 2011 - 01:02 PM, said:
We're testing your internet... not showing you fireworks... stunning graphics get in the way of the test more than anything you've described.. native or not, it's a waste of resources. Why? So it can look pretty. That's the furthest concern from my mind...
Except people don't like things to look like its 1999 anymore.
If you design it properly it doesn't get in the way it actually enhances the experience because you can show users things in a way that looks good but they can understand were just text suffocates the experience.
Figure out how to make a beautiful interface that doesn't get in the way (and you can actually do this) and people will use your app more. I've got a lot of hands on experience with this, in the latest update to one of my apps I improved the UI a lot, didn't change anything else and now I'm making 4 times as much on app sales and the app is getting used 8 times as much. All because I made the UI better.
For you, making a stunning looking website should be #2 on your list just after test accuracy. The UI is what the user sees and interacts with. If it looks like its from 1999 they will use your app/site like its 1999
CA3LE, on 06 October 2011 - 01:02 PM, said:
If you're waiting it's because of the page loads in between things right now... I'll explain in the next section...
Easily solved with more development... development time that I think is better spent on the web application. ...work in some AJAX. Problem solved. ... It's not like its even a problem right now. Seriously, how long do you wait for your results page.... if it takes THAT long then you're getting to see a SECOND benchmark while you wait for something to load that shouldn't take more than a second.

Even when I'm on the shittiest connections the results load instantly for me, so I really don't know what you're talking about there.
I'm not really talking about page loads i'm talking about when you start a test all you see is a progress bar. I have to wait for progress bar then the results page. That would be great for 2005 but its 2011 people want real time results. They want to see the results for the connection instantly from when they push start.
CA3LE, on 06 October 2011 - 01:02 PM, said:
Since when do people hate websites on iPhone and Android? NO NO NO.. you've got it WAY wrong... people hate websites that don't view or or work correctly on those devices. I'm sorry but I'm personally in my browser 100X more than apps. I search the internet before the market or app store. --- There are obviously people out there that think differently from me but my question is... if websites worked better, would they still seek out the market or app store?
Since always. Apple tried to do the mobile app thing it didn't work out to well even for them. Mobile apps are slower, they can't do a 10th what a native app can do. And they are all very basic.
I don't care how much better you make mobile websites, they aren't going to be even remotely close to being able to do what a native app can do anytime soon.
There is a reason why I didn't build a mobile website for my sites and instead built an app.
CA3LE, on 06 October 2011 - 01:02 PM, said:
Yeah, I remember that poorly executed genius idea that came too far ahead of its time... yeah I know what you're talking about. We are on a TOTALLY different infrastructure now. Once symmetrical fiber is commonplace ALL BETS ARE OFF. Video games, graphics editing... I don't care what it is. You'll still be able to compute locally but WHY? If you can do the same thing with nothing more than a input device and monitor. If you think I'm wrong... read this in 5 years.
Having a fast enough connection is only half the problem. The other half if the browser it self. Browsers are insanely slow at executing code. Thats why web apps are still fairly basic in the type of apps you can have in a web browser. They get faster at it all the time with every new version but they are a long way off from being even remotely close to how quickly native code can be executed.
CA3LE, on 06 October 2011 - 01:02 PM, said:
That's true... but why not just build a really bad ass web application... then encapsulate it within a lightweight app that renders the browser? If exposure is the only real benefit...
Been there. Done that. Trust me it doesn't work.
It goes back to the fact that the browser is way too slow. A user will start the app and now has to wait. Because they have to wait for web-kit to initialize, then load the page your telling it to load and then if you have to click anything you have to again wait for the page to load.
It's not the way to do an app.
CA3LE, on 06 October 2011 - 01:02 PM, said:
... I just want to make sure my time gets spent in the right areas. I don't want to have 100 different versions out there... I want ONE unified website. Not a website an two apps, which would surely yield different results from each other... that's not a benchmark.
So do what I did. Build an API. Then everyone is running of the same basic code base on the server and the only thing that is different is the front end on the App and website.
As the person who has the #1 iPad Speedtest app. By not having a dedicated app for TMN your missing out on a lot of faces your Logo could be in front of. As well as a lot of money.
TriRan, on 06 October 2011 - 02:36 PM, said:
well, not exactly but it will be less accurate because it won't be within real world circumstances so it would be a lot like doing a test from a site like speedtest.
That is actually incorrect. It will be more accurate to what your connection is actually doing. Since phones and tablets have really low power CPUs they are unable to max a connection above a specific point this number becomes even less when you add the browser into the factor since the browser engine is really slow.
Just for example the iPhone 3G was only able to get about 5.5 Mbps in the browser no matter how much faster your connection was. But if you ran a native app you could get to about 9 Mbps and thats what the phone was actually able to pull from the wifi connection. The slow CPU combined with the slower browser engine caused inaccurate results.
Since most things that use the internet connection of a phone or tablet are done outside of the browser, the result you get in the browser would be inaccurate to what you are really seeing in the real world.