Mockup
Mockup
What do you guys think?
#pwa
App layout mockups
For me an ergonomic interface is very important and keeping in mind the various ways to use a touchscreen + the desktop interface, I kept the possibility of having multiple layouts to switch to the user's liking.
I didn't know about the plan to replace Goryon, how do you manage to compile it for Play store and the others?
> I didn’t know about the plan to replace Goryon, how do you manage to compile it for Play store and the others?
I _believe_ we can package it up with with Cordova. But first let's just get it working and installed/deployed to
https://yarn.social/app 👌 As it's a PWA it's immediately installable on pretty much every device/os anyway that supports PWA (quite a few now)
> I didn’t know about the plan to replace Goryon, how do you manage to compile it for Play store and the others?
I _believe_ we can package it up with with Cordova. But first let's just get it working and installed/deployed to
https://yarn.social/app 👌 As it's a PWA it's immediately installable on pretty much every device/os anyway that supports PWA (quite a few now)
I also recall Google offering a section dedicated to publishing pure PWAs directly in the Play store but I'm not sure if it's still there.
And also being a PWA could open the possibility of an iOS version too, I don't own any Apple devices so can't help there. 😎
I prefer doing a simple sketch by hand or stylized (like the one I shared) to avoid getting used to a style and then getting stuck to it on any iteration.
To me mockups should be to plan and understand how a pure interface works best and nothing more.
I compare designing then as playing with index cards, you shuffle them, fold them and overlap them.
This is something that those tools never helped me do easily.
I'm also still more than a bit skeptical about going from native to webapp. The webapps on Android tend to open in Chrome and to make it worse, with no option to disable history or other bloat from being saved through it.
I'd love to be proven wrong, but so far I haven't found a PWA that'd work for me right out of the box, without me at best having to wrap it in it's own small browser that isn't chrome, through one of those rather sketchy sites like AppsGeyser.com.
Just don't use them in personal projects! (btw i used Inkscape for mine).
Your concerns about switching to a webapp are not much to worry about if the PWA is made correctly, Here an example i made when building my ParcelJS setup for my office, if you select "Install App" from the tab options it will install like a normal app.
Also AppsGeyser simply wrap with a frame your website, a PWAs is not made that way.
To learn more on PWAs check this out.
Well correctly made or not, if you "install it" directly from a browser, I don't think it'll be as separate as I'd want it to be (not saving shit into browser history, cookies, fill-ins...).
What AppsGeyser does isn't creating a PWA, that's poor wording on my end, but even with well made PWAs, like https://app.revolt.chat, wrapping the web apps site through AppsGeyser ended up being closer to meeting my needs, than using it the intended way, despite it still being even further from native.
It's true that it shares data with chrome since it IS chrome even if installed.
Using Cordova should fill the need of physically separate the app from the browser plus adding an API for native interactions and having more control on the output generated.
Still, the first step is to have the app working. 😜
This time the feed/post layout, with three ideas:
- Focus on content
- Standard card with padding
- Flat full width post (with or without a card, not sure yet)
Hope to hear some feedback from you!
#pwa
Feed/post mockups
Three versions here too:
- A large version
- A smaller version
- A compact but more linear version + links as chips to make them smaller and more "clickable"
Feedback appreciated here too!
#pwa
Profile mockups
Waiting some more feedback from others.
Meanwhile I'll be planning the app feature tree to manage the work.
#pwa