MangoLassi mobile app...
-
@stacksofplates said in MangoLassi mobile app...:
@coliver said in MangoLassi mobile app...:
Why does it need a mobile app? It works really well from my mobile device.
Would be nice for chatting. The chat window on a mobile browser is terrible.
I think they just need to upgrade the chat interface, doesn't need to be natively installed for good functionality.
-
@BBigford said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@coliver said in MangoLassi mobile app...:
Why does it need a mobile app? It works really well from my mobile device.
Would be nice for chatting. The chat window on a mobile browser is terrible.
That's one of the more important for me. I use the chat function quite a bit. Since I don't like having a chat app on my work computer, I use Mango chat since Spiceworks lacks that functionality all together with real time updates.
But it works fine for me... What issues are you having?
Scrolling in a chat window on my iPhone doesn't really work. The text box disappears and will show up depending on how fast I scroll, but I can't click in it. Hard to explain.
-
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@coliver said in MangoLassi mobile app...:
Why does it need a mobile app? It works really well from my mobile device.
Would be nice for chatting. The chat window on a mobile browser is terrible.
I think they just need to upgrade the chat interface, doesn't need to be natively installed for good functionality.
Ya but an app gives you things like offline content. I definitely prefer using the spiceworks app over their mobile site.
-
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@coliver said in MangoLassi mobile app...:
Why does it need a mobile app? It works really well from my mobile device.
Would be nice for chatting. The chat window on a mobile browser is terrible.
I think they just need to upgrade the chat interface, doesn't need to be natively installed for good functionality.
Ya but an app gives you things like offline content. I definitely prefer using the spiceworks app over their mobile site.
I think that the web client can do that too, just chooses not to. Normal web apps have offline options. Don't see why it would be lacking on iOS or Android.
Now is offline content something desired? Maybe, but I doubt by many. It would be kind of nice to see cached content, be able to respond, and have it post later like Facebook... but that doesn't require an app and might cause more problems than it solves.
-
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
@scottalanmiller said in MangoLassi mobile app...:
Now is offline content something desired? Maybe, but I doubt by many.
Chat is the big one in my mind.
-
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
Now is offline content something desired? Maybe, but I doubt by many.
Chat is the big one in my mind.
You want to read chats offline? Makes sense I guess, not one that I would have thought of.
-
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
-
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
-
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@coliver said in MangoLassi mobile app...:
Why does it need a mobile app? It works really well from my mobile device.
Would be nice for chatting. The chat window on a mobile browser is terrible.
I think they just need to upgrade the chat interface, doesn't need to be natively installed for good functionality.
Ya but an app gives you things like offline content. I definitely prefer using the spiceworks app over their mobile site.
The only gripe I have so far (other than the replies are not super intuitive), and the complete lack of a viable chat system, is replying to people has always been non-existant. On the mobile site and in the app. Overall, sub-par on mobile. So I guess not my only gripe, haha.
Can't believe the chat system when you compare it to Mango. Especially the newer version in Mango. Where you can delete chats and such, whereas you couldn't before. Very cool.
-
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
Now is offline content something desired? Maybe, but I doubt by many.
Chat is the big one in my mind.
You want to read chats offline? Makes sense I guess, not one that I would have thought of.
I guess it would be useful to see who chatted you, but you wouldn't be able to stay connected and chat back until you were back online. Same usage as voice the way I see it.
-
@BBigford said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
Now is offline content something desired? Maybe, but I doubt by many.
Chat is the big one in my mind.
You want to read chats offline? Makes sense I guess, not one that I would have thought of.
I guess it would be useful to see who chatted you, but you wouldn't be able to stay connected and chat back until you were back online. Same usage as voice the way I see it.
Ya maybe I'm the only one that looks back through messages. Maybe it's just me but I still have yet to find a mobile site that "felt" as good as an app.
-
Here is an example. When I click the text box in a chat I have to scroll down really far and it ends up doing this:
-
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
Okay, but what's the difference? One depends on the browser, one depends on some other code. Both do the same thing. Native app doesn't do it particularly better, does it? I don't understand the APIs vs hamburger, both do both, right?
-
@stacksofplates said in MangoLassi mobile app...:
@BBigford said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
Now is offline content something desired? Maybe, but I doubt by many.
Chat is the big one in my mind.
You want to read chats offline? Makes sense I guess, not one that I would have thought of.
I guess it would be useful to see who chatted you, but you wouldn't be able to stay connected and chat back until you were back online. Same usage as voice the way I see it.
Ya maybe I'm the only one that looks back through messages. Maybe it's just me but I still have yet to find a mobile site that "felt" as good as an app.
I think that a lot of that is perception. People do different things with native and mobile and so they tend to be different, but not because they have to be.
-
I wonder if a dedicated chat app would be hard? If it could talk to the API of ML, in theory it could be pretty light.
-
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
Okay, but what's the difference? One depends on the browser, one depends on some other code. Both do the same thing. Native app doesn't do it particularly better, does it? I don't understand the APIs vs hamburger, both do both, right?
Well but native gives you things like the roller for selection on iOS, proper integration with other apps for sharing, etc.
-
@scottalanmiller said in MangoLassi mobile app...:
I wonder if a dedicated chat app would be hard? If it could talk to the API of ML, in theory it could be pretty light.
Ya and would in theory work with all NodeBB sites. That would be pretty nice.
Or integrate XMPP.
-
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
Okay, but what's the difference? One depends on the browser, one depends on some other code. Both do the same thing. Native app doesn't do it particularly better, does it? I don't understand the APIs vs hamburger, both do both, right?
Well but native gives you things like the roller for selection on iOS, proper integration with other apps for sharing, etc.
I guess the roller, or whatever it's called, is a bad example because you get that with any selection menu even on a website. But I was thinking more of the sharing functions between applications.
-
@stacksofplates said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
Okay, but what's the difference? One depends on the browser, one depends on some other code. Both do the same thing. Native app doesn't do it particularly better, does it? I don't understand the APIs vs hamburger, both do both, right?
Well but native gives you things like the roller for selection on iOS, proper integration with other apps for sharing, etc.
I guess the roller, or whatever it's called, is a bad example because you get that with any selection menu even on a website. But I was thinking more of the sharing functions between applications.
What does the sharing do? I'm unclear which sharing calls that versus calling something else. Do you have an example application that does that?
-
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
Okay, but what's the difference? One depends on the browser, one depends on some other code. Both do the same thing. Native app doesn't do it particularly better, does it? I don't understand the APIs vs hamburger, both do both, right?
Well but native gives you things like the roller for selection on iOS, proper integration with other apps for sharing, etc.
I guess the roller, or whatever it's called, is a bad example because you get that with any selection menu even on a website. But I was thinking more of the sharing functions between applications.
What does the sharing do? I'm unclear which sharing calls that versus calling something else. Do you have an example application that does that?
For example if I have an image open, I could share it to ML and then pick where I wanted it to go ( thread or chat) vs opening the browser going to the thread and hitting reply, then uploading the image and hitting the submit button.
