3 ms·
We've been working on a very similar idea to this for the past few months: https://pocketweb.io https://pocketweb.io There is a very early iOS beta available,
by shtack 7y ago
We've been working on a very similar idea to this for the past few months: https://pocketweb.io https://pocketweb.io
There is a very early iOS beta available, and Android is coming within the month. We've thought a lot about battery and data and have gotten really good results by leveraging existing radio wakeups, batching requests, and doing all sorts of optimizations to the sites themselves.
Right now we're focused entirely on personal websites, because we believe the majority of those can actually easily be hosted on a phone (eg. How many people actually view your LinkedIn page every day? A single Facebook page doesn't require a datacenter. Etc).
We're limited to single static pages with images right now but better support for multiple pages and server code with SQLite is coming. More template types, for example stores, are coming as well.
Let us know what you think!
- rschulman 7y agoAwesome! I will check it out.
- BMorearty 7y agoCongrats, your site is 100x more comprehensible than the wall of text on the original link. :-)
- baggachipz 7y ago> "When you are ready, turn your PocketWeb site on and you'll a URL that you can share." I think you accidentally a word. Love the project though.
- shtack 7y agoThanks! We'll get that fixed tonight.
- mikenew 7y agoLove the idea. Couple first impressions from the iOS app though: 1. Most of the icons and images are really low-res. You should include @2x, @3x assets or just have higher res images and let them downscale on older devices. 2. A lot of the "Latest Active Sites" won't load, and the spinner just spins forever. I know the whole point is that it's a site hosted on someone's phone and may or may not be available, but there definitely needs to be a more graceful way to fail. The spinner blocks the UI and doesn't go away. I know it's isn't part of the core service you're trying to offer, but seeing blurry buttons and having the app get into a broken state after clicking some links is not a good first impression. There's a lot of signalling involved in the first 30 seconds or so when a user (like me) is trying to decide if they want to invest time and brainpower into exploring your service, and it's worth smoothing those things out.
- shtack 7y agoThanks for the feedback! We're still in very early days with regards to the UI, and I know there's a ton of room for improvement. Hopefully we'll have something more presentable ready soon!