Amazing!
Best Eclipse App
What a horrible thing
What a load of ....
Developer response???? A very long convoluted string of pseudo hypertext??? Meaningless to me.
Total Failure
Doesn't work
Update 8/22: received response from developer but it's just a bunch of useless links. Please advise.
Response from developer
Despite our best efforts, there were some slow service periods on eclipse day for which we sincerely apologize. We were overwhelmed by the response and while our servers managed to keep up most of the time, many of the services that we relied on (e.g. timezone services, contact times, nws forecast) were pushed to the point of breakage. At the peak there were thousands of server calls per second, enough for us to crash the National Weather Service API server. In the last hours before the eclipse alone, our apps were downloaded over 500,000 times. We planned backups to backups, increased capacity as the apps popularity grew but in the end it wasn't enough. We really fought hard to have the best app experience possible. We've learned lessons too and will continue to improve the app for the next eclipse event. I hope you still managed to enjoy the eclipse. Please get in touch with us so we can make it up to you at eclipseapp@simcur.zendesk.com Thank you
Failed when I needed it
Response from developer
Despite our best efforts, there were some slow service periods on eclipse day for which we sincerely apologize. We were overwhelmed by the response and while our servers managed to keep up most of the time, many of the services that we relied on (e.g. timezone services, contact times, nws forecast) were pushed to the point of breakage. At the peak there were thousands of server calls per second, enough for us to crash the National Weather Service API server. In the last hours before the eclipse alone, our apps were downloaded over 500,000 times. We planned backups to backups, increased capacity as the apps popularity grew but in the end it wasn't enough. We really fought hard to have the best app experience possible. We've learned lessons too and will continue to improve the app for the next eclipse event. I hope you still managed to enjoy the eclipse. Please get in touch with us so we can make it up to you at eclipseapp@simcur.zendesk.com Thank you
Not there when you needed it
Didn't work during eclipse time, useless
Response from developer
Despite our best efforts, there were some slow service periods on eclipse day for which we sincerely apologize. We were overwhelmed by the response and while our servers managed to keep up most of the time, many of the services that we relied on (e.g. timezone services, contact times, nws forecast) were pushed to the point of breakage. At the peak there were thousands of server calls per second, enough for us to crash the National Weather Service API server. In the last hours before the eclipse alone, our apps were downloaded over 500,000 times. We planned backups to backups, increased capacity as the apps popularity grew but in the end it wasn't enough. We really fought hard to have the best app experience possible. We've learned lessons too and will continue to improve the app for the next eclipse event. I hope you still managed to enjoy the eclipse. Please get in touch with us so we can make it up to you at eclipseapp@simcur.zendesk.com Thank you
Did they not anticipate the load?
Did they not anticipate and plan for the load of everyone using this app during the eclipse???
Response from developer
Despite our best efforts, there were some slow service periods on eclipse day for which we sincerely apologize. We were overwhelmed by the response and while our servers managed to keep up most of the time, many of the services that we relied on (e.g. timezone services, contact times, nws forecast) were pushed to the point of breakage. At the peak there were thousands of server calls per second, enough for us to crash the National Weather Service API server. In the last hours before the eclipse alone, our apps were downloaded over 500,000 times. We planned backups to backups, increased capacity as the apps popularity grew but in the end it wasn't enough. We really fought hard to have the best app experience possible. We've learned lessons too and will continue to improve the app for the next eclipse event. I hope you still managed to enjoy the eclipse. Please get in touch with us so we can make it up to you at eclipseapp@simcur.zendesk.com Thank you
Not what I would call 'feature rich'
1. Pay for the upgrade, or
2. Don't use it for a solar eclipse
It would seem that their servers are having trouble scaling up for the user load, and as of this instance (1 hour before the eclipse), is not retrieving any data. You would think an app that would be used one in a decade would work during the only time it will be used.
Oh well, guess I'll wait another 99 years to try out the app again after they fix their issues.
Response from developer
Despite our best efforts, there were some slow service periods on eclipse day for which we sincerely apologize. We were overwhelmed by the response and while our servers managed to keep up most of the time, many of the services that we relied on (e.g. timezone services, contact times, nws forecast) were pushed to the point of breakage. At the peak there were thousands of server calls per second, enough for us to crash the National Weather Service API server. In the last hours before the eclipse alone, our apps were downloaded over 500,000 times. We planned backups to backups, increased capacity as the apps popularity grew but in the end it wasn't enough. We really fought hard to have the best app experience possible. We've learned lessons too and will continue to improve the app for the next eclipse event. I hope you still managed to enjoy the eclipse. Please get in touch with us so we can make it up to you at eclipseapp@simcur.zendesk.com Thank you
Map and times not working
-Charleston, SC
Response from developer
Despite our best efforts, there were some slow service periods on eclipse day for which we sincerely apologize. We were overwhelmed by the response and while our servers managed to keep up most of the time, many of the services that we relied on (e.g. timezone services, contact times, nws forecast) were pushed to the point of breakage. At the peak there were thousands of server calls per second, enough for us to crash the National Weather Service API server. In the last hours before the eclipse alone, our apps were downloaded over 500,000 times. We planned backups to backups, increased capacity as the apps popularity grew but in the end it wasn't enough. We really fought hard to have the best app experience possible. We've learned lessons too and will continue to improve the app for the next eclipse event. I hope you still managed to enjoy the eclipse. Please get in touch with us so we can make it up to you at eclipseapp@simcur.zendesk.com Thank you
Itsnotfree
Response from developer
Despite our best efforts, there were some slow service periods on eclipse day for which we sincerely apologize. We were overwhelmed by the response and while our servers managed to keep up most of the time, many of the services that we relied on (e.g. timezone services, contact times, nws forecast) were pushed to the point of breakage. At the peak there were thousands of server calls per second, enough for us to crash the National Weather Service API server. In the last hours before the eclipse alone, our apps were downloaded over 500,000 times. We planned backups to backups, increased capacity as the apps popularity grew but in the end it wasn't enough. We really fought hard to have the best app experience possible. We've learned lessons too and will continue to improve the app for the next eclipse event. I hope you still managed to enjoy the eclipse. Please get in touch with us so we can make it up to you at eclipseapp@simcur.zendesk.com Thank you
Time functions stopped working
Response from developer
Despite our best efforts, there were some slow service periods on eclipse day for which we sincerely apologize. We were overwhelmed by the response and while our servers managed to keep up most of the time, many of the services that we relied on (e.g. timezone services, contact times, nws forecast) were pushed to the point of breakage. At the peak there were thousands of server calls per second, enough for us to crash the National Weather Service API server. In the last hours before the eclipse alone, our apps were downloaded over 500,000 times. We planned backups to backups, increased capacity as the apps popularity grew but in the end it wasn't enough. We really fought hard to have the best app experience possible. We've learned lessons too and will continue to improve the app for the next eclipse event. I hope you still managed to enjoy the eclipse. Please get in touch with us so we can make it up to you at eclipseapp@simcur.zendesk.com Thank you
Fail
Response from developer
Despite our best efforts, there were some slow service periods on eclipse day for which we sincerely apologize. We were overwhelmed by the response and while our servers managed to keep up most of the time, many of the services that we relied on (e.g. timezone services, contact times, nws forecast) were pushed to the point of breakage. At the peak there were thousands of server calls per second, enough for us to crash the National Weather Service API server. In the last hours before the eclipse alone, our apps were downloaded over 500,000 times. We planned backups to backups, increased capacity as the apps popularity grew but in the end it wasn't enough. We really fought hard to have the best app experience possible. We've learned lessons too and will continue to improve the app for the next eclipse event. I hope you still managed to enjoy the eclipse. Please get in touch with us so we can make it up to you at eclipseapp@simcur.zendesk.com Thank you
Not working
Response from developer
Despite our best efforts, there were some slow service periods on eclipse day for which we sincerely apologize. We were overwhelmed by the response and while our servers managed to keep up most of the time, many of the services that we relied on (e.g. timezone services, contact times, nws forecast) were pushed to the point of breakage. At the peak there were thousands of server calls per second, enough for us to crash the National Weather Service API server. In the last hours before the eclipse alone, our apps were downloaded over 500,000 times. We planned backups to backups, increased capacity as the apps popularity grew but in the end it wasn't enough. We really fought hard to have the best app experience possible. We've learned lessons too and will continue to improve the app for the next eclipse event. I hope you still managed to enjoy the eclipse. Please get in touch with us so we can make it up to you at eclipseapp@simcur.zendesk.com Thank you
What is wrong with map location
Response from developer
Thank you. We are updating the geolocation services and the search function will be back up and running soon (today). Thank you for your patience and for using Eclipse Safari.
Was great app, but suddenly does not function
Response from developer
Thank you for your feedback. We are updating the geolocation server today and the search function will be back up and running soon. ps. we were a victim of our own success.
Great app
Response from developer
Thank you for taking the time to leave us a review! We'll look into your request for the field of view information to be displayed onscreen.
Fun companion to Eclipse of the Century!
Start and Stop times are off
Response from developer
Hi, thank you for your report. We've recently changed to a more reliable timezone reference server. If you encounter any issues please feel free to join our Community Forums at the following URL to share experiences, request features and interact with our developers/product experts: https://support.simulationcurriculum.com/hc/en-us/community/topics
